Inspect the health and quality of your Mnemexa workspace memory store. Returns quality score (0-100), total memory count, and breakdown of stale/duplicate/overlong/never-retrieved memories. Use to diagnose memory quality issues.
AI agents call brain.health to retrieve information from Mnemexa MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only diagnostic tool that queries and reports on memory store statistics. It retrieves information about memory health but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could at worst flood logs with excessive health checks or learn details about the memory store structure, but cannot cause damage or irreversible changes.
From the tool's definition Tool description states it "Inspect[s] the health and quality" and "Returns quality score, total memory count, and breakdown" — purely diagnostic retrieval with no modification, deletion, or execution. No side effects or state changes.
Attacks that exploit this kind of access
Inspect the health and quality of your Mnemexa workspace memory store. Returns quality score (0-100), total memory count, and breakdown of stale/duplicate/overlong/never-retrieved memories. Use to diagnose memory quality issues. It is categorised as a Read tool in the Mnemexa MCP MCP Server, which means it retrieves data without modifying state.
Register the Mnemexa MCP server in PolicyLayer and add a rule for brain.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 Mnemexa MCP. Nothing to install.
brain.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 brain.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 brain.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.
brain.health is provided by the Mnemexa MCP server (mnemexa/mcp). 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 →