evaluate_terminal_watch_rules

Evaluate all local terminal notification watch rules against a sample event.

Server Todos @hasna/todos
Category Execute
Risk class High
Parameters 00 required

What evaluate_terminal_watch_rules does on Todos

AI agents invoke evaluate_terminal_watch_rules to trigger actions in Todos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

Why evaluate_terminal_watch_rules needs a policy

This tool actively evaluates/runs watch rules against an event, which constitutes executing logic/rules rather than a passive read. It triggers evaluation of notification rules, which may cause side effects such as firing notifications or alerts. The 'evaluate' action implies running code or rule logic, placing it in the Execute category.

From the tool's definition 'Evaluate all local terminal notification watch rules against a sample event'

Questions about evaluate_terminal_watch_rules

What does the evaluate_terminal_watch_rules tool do? +

Evaluate all local terminal notification watch rules against a sample event. It is categorised as a Execute tool in the Todos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on evaluate_terminal_watch_rules? +

Register the Todos MCP server in PolicyLayer and add a rule for evaluate_terminal_watch_rules: 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 evaluate_terminal_watch_rules? +

evaluate_terminal_watch_rules is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit evaluate_terminal_watch_rules? +

Yes. Add a rate_limit block to the evaluate_terminal_watch_rules 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 evaluate_terminal_watch_rules completely? +

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.