This record as markdown: /tools/ruflo/todo-list.md
What todo_list does on Ruflo
AI agents call todo_list to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why todo_list is rated Low
The tool performs a simple data retrieval function (listing pending tasks) without any capability to modify, delete, execute code, or commit financial transactions. The blast radius of misuse is minimal—an AI agent could only view task information, not alter system state or trigger unintended operations. This is a straightforward Read category tool with low severity.
From the tool's definition Tool name 'todo_list' and description 'List all pending tasks' indicate a retrieval operation with no side effects. This is a query/list operation that reads data without modifying, deleting, or executing external actions.
Attacks that exploit this kind of access
The rule that runs todo_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For todo_list, this is the rule to start with:
todo_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every todo_list call is checked against it from then on.
Questions about todo_list
List all pending tasks. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo MCP server in PolicyLayer and add a rule for todo_list: 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 Ruflo. Nothing to install.
todo_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the todo_list 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 todo_list. 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.
todo_list is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue