update_task_status · Supercoordination MCP Server MCP

WHAT IT DOES

What update_task_status does on Supercoordination MCP Server

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

WHY IT NEEDS A POLICY

Why update_task_status needs a policy

This tool modifies task metadata (status and progress fields) within the collaboration platform. Changes are reversible—statuses can be updated again or reverted. The blast radius is medium: incorrect status updates could mislead team coordination and decision-making, but the core task and data remain intact. It does not delete, execute code, or affect financial systems, placing it firmly in the Write category.

From the tool's definition Tool name 'update_task_status' and description '更新任务状态和进度' (update task status and progress) indicate modification of existing task records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_task_status Rate-limited

update_task_status 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": {
    "update_task_status": {
      "limits": [
        {
          "counter": "update_task_status_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 Supercoordination MCP Server, so you can run agents against it safely.

FAQ

Questions about update_task_status

What does the update_task_status tool do? +

更新任务状态和进度. It is categorised as a Write tool in the Supercoordination 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 update_task_status? +

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

What risk level is update_task_status? +

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

Can I rate-limit update_task_status? +

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

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

update_task_status is provided by the Supercoordination MCP Server MCP server (vionwilliams/supercoordination-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.