Get a saved packing template by name or trip_type, or save a new one. Use before a trip to print a checklist.
AI agents use packing_list 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.
The tool has dual functionality: reading (get a saved packing template) and writing (save a new one). Per the rules, the most severe applicable category wins, making this Write. The blast radius is low since packing list data is non-sensitive personal planning information with no financial, destructive, or executable implications.
From the tool's definition 'or save a new one' indicates this tool can create/modify stored packing templates in addition to reading them
Attacks that exploit this kind of access
Get a saved packing template by name or trip_type, or save a new one. Use before a trip to print a checklist. 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 packing_list: 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.
packing_list 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 packing_list 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 packing_list. 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.
packing_list 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 →