Get comprehensive project overview including recent memories, active tasks, and project statistics.
AI agents call get_project_context to retrieve information from AgentCortex MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely fetches and aggregates existing project data for display/review purposes. It has no capability to create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could retrieve more context than intended, but cannot damage systems or data. Categorized as Read with low severity.
From the tool's definition Tool retrieves 'comprehensive project overview including recent memories, active tasks, and project statistics' with no mention of modification, deletion, or side effects.
Attacks that exploit this kind of access
Get comprehensive project overview including recent memories, active tasks, and project statistics. It is categorised as a Read tool in the AgentCortex MCP MCP Server, which means it retrieves data without modifying state.
Register the AgentCortex 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 AgentCortex MCP. 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 AgentCortex MCP server (sage-hq/agentcortex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_project_context is one line of AgentCortex's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →