daa_agent_adapt
Trigger agent adaptation based on feedback Use when native Task is wrong because you need agents that adapt their cognitive pattern (convergent / divergent / lateral / systems / critical) per-task and share knowledge across the swarm. For static one-shot agents, native Task is fine.
This record as markdown: /tools/io-github-ruvnet-claude-flow/daa-agent-adapt.md
What daa_agent_adapt does on Claude Flow
AI agents invoke daa_agent_adapt to trigger actions in Claude Flow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why daa_agent_adapt is rated High
This tool executes external operations (agent adaptation and knowledge-sharing across a swarm) whose effects depend on feedback arguments. While it does not directly delete data or move money, it modifies the operational behavior of an agent fleet in ways that could have unintended consequences if misapplied by an AI—for example, adapting agents to harmful cognitive patterns or triggering uncontrolled swarm behavior.
From the tool's definition Trigger agent adaptation—the tool initiates dynamic modifications to agent behavior patterns. The description indicates it causes agents to 'adapt their cognitive pattern' and 'share knowledge across the swarm,' which are runtime behavioral changes triggered…
Attacks that exploit this kind of access
The rule that runs daa_agent_adapt safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For daa_agent_adapt, this is the rule to start with:
daa_agent_adapt stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every daa_agent_adapt call is checked against it from then on.
Questions about daa_agent_adapt
Trigger agent adaptation based on feedback Use when native Task is wrong because you need agents that adapt their cognitive pattern (convergent / divergent / lateral / systems / critical) per-task and share knowledge across the swarm. For static one-shot agents, native Task is fine. It is categorised as a Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Flow MCP server in PolicyLayer and add a rule for daa_agent_adapt: 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.
daa_agent_adapt is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the daa_agent_adapt 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.
Set action: deny in the PolicyLayer policy for daa_agent_adapt. 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.
daa_agent_adapt 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.
Across the catalogue