todo_complete

Mark a task as complete

SERVERRuflo SOURCEruvnet/ruflo

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ruflo/todo-complete.md

WHAT IT DOES

What todo_complete does on Ruflo

AI agents use todo_complete to create or update resources in Ruflo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ruflo environment.

RISK

Why todo_complete is rated Medium

This tool creates or modifies data reversibly by updating a task's completion status. It does not execute arbitrary code, delete data irreversibly, or move money. The operation can be undone by marking the task incomplete again. Given the low-risk nature of task state modifications and the limited blast radius of misuse (a task incorrectly marked complete), severity is low.

From the tool's definition Tool name 'todo_complete' and description 'Mark a task as complete' indicate a state change operation that modifies task records.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs todo_complete 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_complete, this is the rule to start with:

todo_complete Rate-limited

todo_complete stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "todo_complete": {
      "limits": [
        {
          "counter": "todo_complete_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about todo_complete

What does the todo_complete tool do? +

Mark a task as complete. It is categorised as a Write tool in the Ruflo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on todo_complete? +

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

What risk level is todo_complete? +

todo_complete is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit todo_complete? +

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

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

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

KEEP EXPLORING

More on Ruflo, and thousands of servers like it.

This server

All 496 Ruflo tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →