Returns the current working memory (Layer 1) as formatted text.
AI agents call cortex_get_context to retrieve information from Cortex Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves stored memory/context data without modifying, deleting, or executing any operations. It is a straightforward read operation that poses minimal risk if invoked by an AI agent. The low severity reflects that exposure of project memory, while sensitive, does not cause irreversible damage or external execution.
From the tool's definition Tool name 'cortex_get_context' and description 'Returns the current working memory (Layer 1) as formatted text' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access cortex_get_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cortex Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for cortex_get_context:
{
"version": "1",
"default": "deny",
"tools": {
"cortex_get_context": {}
}
}cortex_get_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the current working memory (Layer 1) as formatted text. It is categorised as a Read tool in the Cortex Memory MCP Server, which means it retrieves data without modifying state.
Register the Cortex Memory MCP server in PolicyLayer and add a rule for cortex_get_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 Cortex Memory. Nothing to install.
cortex_get_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 cortex_get_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 cortex_get_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.
cortex_get_context is provided by the Cortex Memory MCP server (skullfire07/cortex-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cortex Memory, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Cortex Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.