AI agents use set_terminal_notification_rule 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 notification preferences/rules in a reversible manner (rules can be deleted or updated again), making it a Write operation. Severity is medium because misconfigured notification rules could cause notification spam or missed alerts, affecting task management workflow, but the impact is limited to the local user's notification settings and is easily correctable.
From the tool's definition Tool description states 'Create or update a local terminal notification watch rule' - the verbs 'create' and 'update' indicate reversible modification of configuration data (notification rules).
Attacks that exploit this kind of access
Create or update a local terminal notification watch rule 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_terminal_notification_rule: 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_terminal_notification_rule 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_terminal_notification_rule 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_terminal_notification_rule. 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_terminal_notification_rule 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.
set_terminal_notification_rule is one line of Todos's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →