Returns the generated .project.md content for the repository.
AI agents call read_project_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 retrieves structured project memory and metadata from a file (.project.md). It has no side effects, does not execute code, does not modify data, and does not trigger external operations. It falls squarely into the Read category. Severity is low because exposure of project context metadata poses minimal risk; it is descriptive documentation rather than sensitive credentials or destructive capability.
From the tool's definition Tool name 'read_project_context' and description 'Returns the generated .project.md content' indicate a retrieval operation with no modification or execution. The action is purely informational—reading project metadata.
Attacks that exploit this kind of access
Returns the generated .project.md content for the repository. 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 read_project_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.
read_project_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 read_project_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 read_project_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.
read_project_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 →