Analyze saved memory health across all projects and sessions. Reports duplicates,
AI agents call get_memory_health to retrieve information from Memory Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_memory_health performs diagnostic analysis and reporting on existing memory data. It retrieves and examines information but does not create, modify, delete, or execute operations. The tool has minimal blast radius if misused by an AI agent — it can only return analysis results. This clearly fits the Read category (queries/retrieves data with no side effects).
From the tool's definition Tool description states 'Analyze saved memory health across all projects and sessions' and 'Reports duplicates' — these are read/analysis operations with no data modification, creation, deletion, or execution of external operations.
Attacks that exploit this kind of access
Analyze saved memory health across all projects and sessions. Reports duplicates,. It is categorised as a Read tool in the Memory Bridge MCP Server, which means it retrieves data without modifying state.
Register the Memory Bridge MCP server in PolicyLayer and add a rule for get_memory_health: 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 Memory Bridge. Nothing to install.
get_memory_health 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_memory_health 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_memory_health. 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_memory_health is provided by the Memory Bridge MCP server (lewenw/claude-memory-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →