tasks_complete · Tasks MCP Server MCP: Risk & Policy

WHAT IT DOES

What tasks_complete does on Tasks MCP Server

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

WHY IT NEEDS A POLICY

Why tasks_complete needs a policy

This tool modifies task state reversibly—a completed task can be marked incomplete again. While it updates data, it is not destructive (no deletion), does not execute arbitrary code, and has no financial impact. The blast radius is minimal since toggling task completion status poses low risk even if misused by an agent.

From the tool's definition Tool description states 'Mark a task as completed' and returns 'The updated task', indicating a reversible modification of task state. The operation changes data (task status) but does not delete or destroy the task record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tasks_complete Rate-limited

tasks_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": {
    "tasks_complete": {
      "limits": [
        {
          "counter": "tasks_complete_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 Tasks MCP Server, so you can run agents against it safely.

FAQ

Questions about tasks_complete

What does the tasks_complete tool do? +

Mark a task as completed. Args: - id (required): Task ID to complete Returns: The updated task, or an error if the task was not found. It is categorised as a Write tool in the Tasks 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 tasks_complete? +

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

What risk level is tasks_complete? +

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

Can I rate-limit tasks_complete? +

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

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

tasks_complete is provided by the Tasks MCP Server MCP server (maxouverzou/tasks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.