Check whether Mnemexa is connected and report the active workspace, plan, and API key prefix. Useful for verifying setup end-to-end against the live backend.
AI agents call brain.status 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 tool queries system state and returns read-only diagnostic information. It neither modifies data, executes arbitrary code, deletes resources, nor moves money. The exposure of an API key prefix in output is a security concern but does not elevate the tool's functional category beyond Read. Severity is low because misuse is limited to information disclosure about the user's setup and connection status.
From the tool's definition Tool name 'brain.status' and description indicate it 'check[s] whether Mnemexa is connected and report[s]' configuration details—a retrieval operation with no modification or execution of external code.
Attacks that exploit this kind of access
Check whether Mnemexa is connected and report the active workspace, plan, and API key prefix. Useful for verifying setup end-to-end against the live backend. 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.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 Mnemexa MCP. Nothing to install.
brain.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 brain.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 brain.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.
brain.status 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 →