Critical in-case-of information: who to call, where the will is, spare key locations, kids
AI agents call emergency_info to retrieve information from Personal Brain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves personally important reference data in an emergency context. While sensitive, it is fundamentally a read operation that queries stored information without side effects, modification, deletion, or execution of external operations. The low severity reflects that misuse results in information disclosure rather than data destruction, financial loss, or irreversible harm.
From the tool's definition Tool name 'emergency_info' and description indicate retrieval of stored critical information (who to call, will location, spare key locations, kids) with no modification or destructive action described.
Attacks that exploit this kind of access
Critical in-case-of information: who to call, where the will is, spare key locations, kids. It is categorised as a Read tool in the Personal Brain MCP Server, which means it retrieves data without modifying state.
Register the Personal Brain MCP server in PolicyLayer and add a rule for emergency_info: 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 Personal Brain. Nothing to install.
emergency_info 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 emergency_info 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 emergency_info. 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.
emergency_info is provided by the Personal Brain MCP server (phantomts/personal-brain-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 →