toggle_task_completion · Tududi MCP Server MCP

WHAT IT DOES

What toggle_task_completion does on Tududi MCP Server

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

WHY IT NEEDS A POLICY

Why toggle_task_completion needs a policy

This tool modifies task data reversibly by changing a task's completion flag. While the state change is persistent in the system, it is not destructive—toggling a completed task back to open or vice versa can be easily reversed, classifying it as Write rather than Destructive.

From the tool's definition toggle_task_completion toggles the completion status of a task, which modifies the task's state reversibly (completed → open or vice versa). The description explicitly states it 'mark[s] as completed or reopen[s]', indicating a state change that can be undone.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

toggle_task_completion Rate-limited

toggle_task_completion 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": {
    "toggle_task_completion": {
      "limits": [
        {
          "counter": "toggle_task_completion_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tududi MCP Server, so you can run agents against it safely.

FAQ

Questions about toggle_task_completion

What does the toggle_task_completion tool do? +

Toggle the completion status of a task (mark as completed or reopen). Uses numeric task ID. It is categorised as a Write tool in the Tududi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on toggle_task_completion? +

Register the Tududi MCP Server MCP server in PolicyLayer and add a rule for toggle_task_completion: 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 Tududi MCP Server. Nothing to install.

What risk level is toggle_task_completion? +

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

Can I rate-limit toggle_task_completion? +

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

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

toggle_task_completion is provided by the Tududi MCP Server MCP server (jeanbispo/tududi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.