AI agents use create_handoff_packet to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
This tool creates and writes a new data structure (handoff packet) to local storage. This is a reversible write operation with no destructive or financial impact. The 'medium' severity reflects that misuse could create unwanted handoff packets that clutter the system or misdirect work, but the impact is limited to local data creation without cascading external effects.
From the tool's definition The tool description states it "Build[s] and persist[s] a handoff packet locally" — the verbs "build" and "persist" indicate creation and storage of data. The context of a task management system suggests this creates handoff records or state artifacts.
Attacks that exploit this kind of access
Build and persist a handoff packet locally. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for create_handoff_packet: 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 Todos. Nothing to install.
create_handoff_packet 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 create_handoff_packet 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 create_handoff_packet. 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.
create_handoff_packet is provided by the Todos MCP server (@hasna/todos). 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 →