New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

swarm_pheromone_update

Record a normalized per-agent task outcome for a running pheromone-adaptive swarm. Use when a static agent pool is wrong because repeated task evidence should update role-aware EMA fitness and produce a bounded keep/suspend/reactivate decision; native Task has no persistent swarm eligibility gate.

SERVERClaude Flow SOURCEclaude-flow
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/swarm-pheromone-update.md

What swarm_pheromone_update does on Claude Flow

AI agents use swarm_pheromone_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 swarm_pheromone_update is rated Medium

This tool writes to swarm agent state and fitness metrics, causing state mutations that affect which agents are active. It updates EMA (exponential moving average) fitness scores and produces membership decisions (keep/suspend/reactivate), making it a Write operation. It is not Destructive because fitness updates and role suspensions are conceptually reversible or can be overridden by subsequent updates.

From the tool's definition Tool description: 'Record a normalized per-agent task outcome... should update role-aware EMA fitness and produce a bounded keep/suspend/reactivate decision.' The verb 'update' and 'record' indicate modification of persistent state (agent fitness metrics,…

Questions about swarm_pheromone_update

What does the swarm_pheromone_update tool do? +

Record a normalized per-agent task outcome for a running pheromone-adaptive swarm. Use when a static agent pool is wrong because repeated task evidence should update role-aware EMA fitness and produce a bounded keep/suspend/reactivate decision; native Task has no persistent swarm eligibility gate. 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 swarm_pheromone_update? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for swarm_pheromone_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 swarm_pheromone_update? +

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

Can I rate-limit swarm_pheromone_update? +

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

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

swarm_pheromone_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.

More on Claude Flow, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude Flow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.