Event-invoked checklists (morning routine, leaving for a trip, closing the cabin). Manage routines and their ordered steps.
AI agents use routines to create or update resources in Personal Brain — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Personal Brain environment.
This tool modifies personal routine data within the user's personal-brain database. While it creates or updates structured checklist information, it does not execute external commands, delete data irreversibly, or affect financial/critical systems. The blast radius of misuse is limited to corrupting or altering personal routine records, which are reversible. Hence, Write is the appropriate category with low severity.
From the tool's definition Tool description explicitly states 'Manage routines and their ordered steps,' indicating creation and modification of routine data.
Attacks that exploit this kind of access
Event-invoked checklists (morning routine, leaving for a trip, closing the cabin). Manage routines and their ordered steps. It is categorised as a Write tool in the Personal Brain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Personal Brain MCP server in PolicyLayer and add a rule for routines: 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.
routines is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the routines 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 routines. 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.
routines 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 →