agent_update · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What agent_update does on Claude Flow

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

WHY IT NEEDS A POLICY

Why agent_update needs a policy

This tool modifies agent state/configuration without deletion. While the context (agent orchestration in a 'hive-mind swarms' system) suggests agents could be autonomous, the description 'mutate a tracked agent' indicates a write rather than execute operation—it changes agent properties rather than triggering arbitrary code execution.

From the tool's definition Tool name: agent_update. Description: 'Mutate a tracked agent.' The verb 'mutate' indicates modification of an existing agent's state or configuration. This is a reversible write operation that alters tracked agent data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

agent_update Rate-limited

agent_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": {
    "agent_update": {
      "limits": [
        {
          "counter": "agent_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 Claude Flow, so you can run agents against it safely.

FAQ

Questions about agent_update

What does the agent_update tool do? +

Mutate a tracked agent\. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on agent_update? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for agent_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 Claude Flow. Nothing to install.

What risk level is agent_update? +

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

Can I rate-limit agent_update? +

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

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

agent_update is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.