# Request Context Module Methods
The request context object (`event` parameter received in handlers/layouts/views) has also been expanded to have the following module methods:
* `getCurrentModule()` : Returns the module name of the currently executing module event.
* `getModuleRoot([moduleName])` : Returns the web accessible root to the modules root directory. If you do not pass the explicit module name, we will default to use the `getCurrentModule()` in the request.
The last method is what is really interesting when building visual modules that need assets from within the module itself. You can easily target the web-accessible path to the module by using the `getModuleRoot()` method. Below are some examples:
```javascript
<---< Base HREF if using SES --->
<---
<---< Module Javascript --->
The Awesome ForgeBox Module!
```
As you can see, this is essential when building module UIs or layouts.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://coldbox.ortusbooks.com/v4.x-1/hmvc/modules/request-context-module-methods.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.