context
A read tool on the Claude Engram MCP server.
This record as markdown: /tools/20alexl-claude-engram/context.md
What context does on Claude Engram
AI agents call context to retrieve information from Claude Engram without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why context is rated Low
Based on the server's stated purpose (auto-tracking, cross-session search, pattern mining) and the pattern of sibling tools, 'context' most likely retrieves or queries stored session context/history rather than modifying or executing operations. However, confidence is notably reduced due to the empty description, which prevents direct verification of function and scope.
From the tool's definition Tool name 'context' with empty description; sibling tools suggest read operations (find_similar_issues, audit_batch, deps_map, file_summarize) that retrieve and analyze session/code data.
Attacks that exploit this kind of access
The rule that runs context safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Engram, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For context, this is the rule to start with:
context is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Engram, apply this rule, and every context call is checked against it from then on.
Questions about context
context is a read tool on the Claude Engram MCP server. It is categorised as a Read tool in the Claude Engram MCP Server, which means it retrieves data without modifying state.
Register the Claude Engram MCP server in PolicyLayer and add a rule for 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 Claude Engram. Nothing to install.
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 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 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.
context is provided by the Claude Engram MCP server (20alexl/claude-engram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Engram, and thousands of servers like it.
This server
Across the catalogue