Return context for a module or feature area, including module summary, files, recent commits, and likely impact paths.
AI agents call get_module_context to retrieve information from Project Context Map without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval and analysis tasks (get_module_context, returning summary/files/commits/paths) without creating, modifying, deleting, or executing code. It is a passive query operation similar to sibling tools like query_topology and read_project_context.
From the tool's definition Tool retrieves and returns context information: 'module summary, files, recent commits, and likely impact paths' — all read-only queries with no side effects or modifications.
Attacks that exploit this kind of access
Return context for a module or feature area, including module summary, files, recent commits, and likely impact paths. It is categorised as a Read tool in the Project Context Map MCP Server, which means it retrieves data without modifying state.
Register the Project Context Map 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 Project Context Map. 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 Project Context Map MCP server (tamojit-123/project-context-map-mcp). 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 →