task_update · Lockstep MCP: Risk & Policy

WHAT IT DOES

What task_update does on Lockstep

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

WHY IT NEEDS A POLICY

Why task_update needs a policy

The tool creates or modifies data (task state) in a reversible manner. It does not execute code, delete data irreversibly, or move financial resources. This is a classic Write operation common in project management and coordination systems. The severity is medium because task state corruption could cause workflow issues and confusion among coordinating AI agents, but changes are reversible via subsequent updates.

From the tool's definition Tool description states 'Update a task' - this modifies existing task data. The sibling tools on the server include destructive operations (command_run could execute arbitrary commands) and file locks, suggesting this is a collaborative coordination system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

task_update Rate-limited

task_update 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": {
    "task_update": {
      "limits": [
        {
          "counter": "task_update_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 Lockstep, so you can run agents against it safely.

FAQ

Questions about task_update

What does the task_update tool do? +

Update a task. It is categorised as a Write tool in the Lockstep MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on task_update? +

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

What risk level is task_update? +

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

Can I rate-limit task_update? +

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

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

task_update is provided by the Lockstep MCP server (tmmoore286/lockstep-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.