claude_engram_status
Check Claude Engram health. Returns: status, model, memory stats.
This record as markdown: /tools/20alexl-claude-engram/claude-engram-status.md
What claude_engram_status does on Claude Engram
AI agents call claude_engram_status 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 claude_engram_status is rated Low
This tool queries system health and statistics without modifying, executing, or deleting any data. It is a diagnostic read operation that returns monitoring information about the Claude Engram service state.
From the tool's definition Tool name includes 'status' and description explicitly states 'Check' and 'Returns: status, model, memory stats' — pure retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs claude_engram_status 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 claude_engram_status, this is the rule to start with:
claude_engram_status 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 claude_engram_status call is checked against it from then on.
Questions about claude_engram_status
Check Claude Engram health. Returns: status, model, memory stats. 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 claude_engram_status: 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.
claude_engram_status 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 claude_engram_status 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 claude_engram_status. 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.
claude_engram_status 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