update_task · Schedule Task MCP: Risk & Policy

WHAT IT DOES

What update_task does on Schedule Task MCP

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

WHY IT NEEDS A POLICY

Why update_task needs a policy

update_task creates or modifies task metadata (schedule, instructions, trigger_type/trigger_config) in a reversible manner. It does not delete tasks (that is delete_task's role), does not execute arbitrary code (that is execute_task's role), and does not move money.

From the tool's definition Tool name 'update_task' and description explicitly states 'Modify an existing task (schedule, instructions)' — this is a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_task Rate-limited

update_task 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": {
      "limits": [
        {
          "counter": "update_task_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 Schedule Task MCP, so you can run agents against it safely.

FAQ

Questions about update_task

What does the update_task tool do? +

Modify an existing task (schedule, instructions). Flow: confirm the user really means to edit the schedule, call get_current_time when the timing changes, adjust trigger_type/trigger_config accordingly, and return the updated summary. It is categorised as a Write tool in the Schedule Task 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? +

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

What risk level is update_task? +

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

Can I rate-limit update_task? +

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

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

update_task is provided by the Schedule Task MCP server (liao1fan/schedule-task-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.