View or modify the meal plan. action=get returns the plan for the next N days. action=set assigns a recipe (or freeform text) to a date+slot. action=clear removes a slot.
AI agents use meal_plan 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 primarily performs write operations: setting/assigning meal plan entries and clearing slots are reversible data modifications. The 'get' action is read-only, but the tool's primary purpose includes modification capability. This is classified as Write rather than Execute because it modifies structured personal data (meal planning) rather than running arbitrary code or external operations.
From the tool's definition Tool description states it can 'modify the meal plan' with actions including 'action=set assigns a recipe (or freeform text) to a date+slot' and 'action=clear removes a slot.' These are reversible modifications.
Attacks that exploit this kind of access
View or modify the meal plan. action=get returns the plan for the next N days. action=set assigns a recipe (or freeform text) to a date+slot. action=clear removes a slot. 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 meal_plan: 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.
meal_plan 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 meal_plan 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 meal_plan. 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.
meal_plan 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 →