New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_terminal_notification_rule

Remove a configured local terminal notification watch rule.

SERVERTodos SOURCE@hasna/todos
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/todos/remove-terminal-notification-rule.md

What remove_terminal_notification_rule does on Todos

AI agents call remove_terminal_notification_rule to permanently remove resources in Todos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove_terminal_notification_rule is rated Critical

The tool permanently removes/deletes a configured notification rule, which is an irreversible deletion of a configuration item. While the blast radius is limited (only affects terminal notification rules), the action cannot be undone without reconfiguring the rule manually.

From the tool's definition "Remove a configured local terminal notification watch rule"

Questions about remove_terminal_notification_rule

What does the remove_terminal_notification_rule tool do? +

Remove a configured local terminal notification watch rule. It is categorised as a Destructive tool in the Todos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_terminal_notification_rule? +

Register the Todos MCP server in PolicyLayer and add a rule for remove_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.

What risk level is remove_terminal_notification_rule? +

remove_terminal_notification_rule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_terminal_notification_rule? +

Yes. Add a rate_limit block to the remove_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.

How do I block remove_terminal_notification_rule completely? +

Set action: deny in the PolicyLayer policy for remove_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.

What MCP server provides remove_terminal_notification_rule? +

remove_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.

More on Todos, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Todos's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.