update_task_status · Agent-Comm-Hub MCP: Risk & Policy

WHAT IT DOES

What update_task_status does on Agent-Comm-Hub

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

WHY IT NEEDS A POLICY

Why update_task_status needs a policy

This tool creates or modifies task state reversibly. It updates task execution status (including progress reports via 'in_progress + progress') and triggers notifications. These are write operations—the modifications can be undone or corrected with follow-up status updates.

From the tool's definition Tool name 'update_task_status' combined with description indicating it modifies task execution status ('更新任务执行状态') and triggers real-time notifications ('自动实时通知发起方'). This is a state modification operation.

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 Agent-Comm-Hub, so you can run agents against it safely.

FAQ

Questions about update_task_status

What does the update_task_status tool do? +

更新任务执行状态，自动实时通知发起方。支持中途汇报进度（in_progress + progress）。. It is categorised as a Write tool in the Agent-Comm-Hub 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 Agent-Comm-Hub 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 Agent-Comm-Hub. 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 Agent-Comm-Hub MCP server (liuboacean/agent-comm-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.