Get detailed context for a specific module by ID or file path. Use list_modules first to see available modules.
AI agents call get_module_context to retrieve information from Open Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/retrieval operation on project documentation and module information. It takes a module ID or file path as input and returns detailed context about that module. There are no side effects, no data modification, no code execution, and no destructive operations.
From the tool's definition The tool description explicitly states "Get detailed context" for a module, indicating it retrieves and returns information without modification.
Attacks that exploit this kind of access
Get detailed context for a specific module by ID or file path. Use list_modules first to see available modules. It is categorised as a Read tool in the Open Context MCP Server, which means it retrieves data without modifying state.
Register the Open Context MCP server in PolicyLayer and add a rule for get_module_context: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Open Context. Nothing to install.
get_module_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_module_context rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_module_context. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_module_context is provided by the Open Context MCP server (niawjunior/opencontext). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →