AI agents use set_local_event_hook 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 modifies system state by creating or updating event hooks, which are configuration elements. While it doesn't delete data (ruling out Destructive), it doesn't merely query data (Read), nor does it execute arbitrary code (Execute would require triggering external operations based on variable arguments). The hook creation/update is reversible—hooks can be removed or modified later.
From the tool's definition Tool description states 'Create or update a local event hook' - this is a reversible modification operation that creates or modifies configuration/hooks. The verb 'Create or update' is characteristic of Write-category tools.
Attacks that exploit this kind of access
Create or update a local event hook for task, plan, run, approval, import, or export events. 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 set_local_event_hook: 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.
set_local_event_hook 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 set_local_event_hook 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 set_local_event_hook. 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.
set_local_event_hook 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 →