Get the full context document (llms.txt format) for a project. This includes project description, architecture, and all module contexts. Use resolve_project first to get the project ID.
AI agents call get_project_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 retrieves and queries project documentation and context information. It performs no modifications, deletions, or external operations—purely a read operation on codebase metadata. The low severity reflects that exposure of project documentation, while potentially sensitive, does not directly enable data modification or system compromise.
From the tool's definition Tool description states it 'Get[s] the full context document' and 'includes project description, architecture, and all module contexts.' The verb 'get' and the read-only nature of retrieving documentation indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Get the full context document (llms.txt format) for a project. This includes project description, architecture, and all module contexts. Use resolve_project first to get the project ID. 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_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 Open Context. Nothing to install.
get_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 get_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 get_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.
get_project_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 →