get_current_state

Snapshot of the user.s current life state: active projects, current meds, active subscriptions, pets, vehicles, properties, next trip. The

Server Personal Brain phantomts/personal-brain-mcp
Category Read
Risk class Low
Parameters 00 required

What get_current_state does on Personal Brain

AI agents call get_current_state 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.

Why get_current_state needs a policy

This tool retrieves personal information without modifying or executing anything. However, severity is high rather than low because the data returned (medications, subscriptions, properties, travel plans) is sensitive and could enable harmful activities if misused by an AI agent (e.g., identity theft, physical harm, stalking). The blast radius of exposure is significant despite the read-only nature.

From the tool's definition Tool description explicitly states it retrieves a 'Snapshot of the user's current life state' including active projects, medications, subscriptions, pets, vehicles, properties, and travel plans. No modification, deletion, or execution verbs present.

Questions about get_current_state

What does the get_current_state tool do? +

Snapshot of the user.s current life state: active projects, current meds, active subscriptions, pets, vehicles, properties, next trip. The. It is categorised as a Read tool in the Personal Brain MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_current_state? +

Register the Personal Brain MCP server in PolicyLayer and add a rule for get_current_state: 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.

What risk level is get_current_state? +

get_current_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_current_state? +

Yes. Add a rate_limit block to the get_current_state 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.

How do I block get_current_state completely? +

Set action: deny in the PolicyLayer policy for get_current_state. 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.

What MCP server provides get_current_state? +

get_current_state 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.