Returns a compressed briefing of the project as a Markdown string: active modules, recent decisions, and open problems.
AI agents call get_project_context to retrieve information from Memex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a temporal knowledge graph to retrieve and summarize existing project context (modules, decisions, problems). It has no capability to modify data, execute code, delete records, or trigger external operations. The blast radius of misuse is minimal—an AI agent could only receive potentially stale or incomplete context information, which does not compromise system integrity or enable harmful actions.
From the tool's definition Tool description states it 'Returns a compressed briefing' — a retrieval operation with no modification or side effects. The name 'get_' prefix and verb 'Returns' confirm read-only semantics.
Documented attack patterns abuse exactly the kind of access get_project_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memex, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_context": {}
}
}get_project_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 a compressed briefing of the project as a Markdown string: active modules, recent decisions, and open problems. It is categorised as a Read tool in the Memex MCP Server, which means it retrieves data without modifying state.
Register the Memex 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 Memex. 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 Memex MCP server (stifler7/memex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memex, 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.
13 Memex tools catalogued and risk-classified — across an index of 43,000+ MCP servers.