patrol_tasks

Scan for task issues: stuck tasks, low-confidence completions, orphaned tasks, zombie-blocked tasks, and pending reviews.

SERVERTodos SOURCE@hasna/todos

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/todos/patrol-tasks.md

WHAT IT DOES

What patrol_tasks does on Todos

AI agents call patrol_tasks to retrieve information from Todos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why patrol_tasks is rated Low

This tool retrieves and analyzes task status information to identify problematic patterns, but does not create, modify, delete, or execute operations. It is a diagnostic/monitoring tool that fits the 'Read' category as it queries task state without causing changes.

From the tool's definition 'Scan for task issues' indicates the tool performs analysis and monitoring without modifying data. It checks for conditions like stuck tasks, low-confidence completions, orphaned tasks, zombie-blocked tasks, and pending reviews—all observational queries with…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs patrol_tasks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For patrol_tasks, this is the rule to start with:

patrol_tasks Allowed

patrol_tasks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "patrol_tasks": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every patrol_tasks call is checked against it from then on.

FAQ

Questions about patrol_tasks

What does the patrol_tasks tool do? +

Scan for task issues: stuck tasks, low-confidence completions, orphaned tasks, zombie-blocked tasks, and pending reviews. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on patrol_tasks? +

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

patrol_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit patrol_tasks? +

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

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

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

KEEP EXPLORING

More on Todos, and thousands of servers like it.

This server

All 528 Todos tools →

Across the catalogue

list_tasks on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →