Maintenance tasks (HVAC filters, septic, gutters, vehicle service). action=get lists due within N days, log_done records completion and rolls next_due_at, add creates a recurring task.
AI agents use maintenance_schedule 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 both reads (action=get lists due tasks) and writes data (log_done records completion and updates next_due_at, add creates new recurring tasks). Per the rules, Write is the most severe applicable category here. Misuse could corrupt maintenance schedules or create spurious tasks, but data is reversible and there's no destructive, financial, or execution risk.
From the tool's definition log_done records completion and rolls next_due_at, add creates a recurring task
Attacks that exploit this kind of access
Maintenance tasks (HVAC filters, septic, gutters, vehicle service). action=get lists due within N days, log_done records completion and rolls next_due_at, add creates a recurring task. 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 maintenance_schedule: 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.
maintenance_schedule 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 maintenance_schedule 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 maintenance_schedule. 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.
maintenance_schedule 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 →