update_task_status · AgentCortex MCP: Risk & Policy

WHAT IT DOES

What update_task_status does on AgentCortex MCP

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

WHY IT NEEDS A POLICY

Why update_task_status needs a policy

This tool creates or modifies task metadata within the memory system. It is clearly a Write operation because it updates existing records, and the effects are reversible. The blast radius is minimal since it only affects internal task status tracking within an isolated project context, with no cascading side effects, financial impact, or irreversible data loss.

From the tool's definition Tool name 'update_task_status' and description 'Update the status of an existing task' indicate modification of data. The action is reversible (status can be changed again), non-destructive, and does not execute code or trigger external operations.

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 AgentCortex MCP, so you can run agents against it safely.

FAQ

Questions about update_task_status

What does the update_task_status tool do? +

Update the status of an existing task. Use this to track progress and mark tasks as completed. It is categorised as a Write tool in the AgentCortex MCP 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 AgentCortex 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 AgentCortex MCP. 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 AgentCortex MCP server (sage-hq/agentcortex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.