Share knowledge between agents 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.
AI agents use daa_knowledge_share to create or update resources in Ruflo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ruflo environment.
The tool writes knowledge state to multiple agents across the swarm, modifying their cognitive/memory state. It is not merely reading data — it actively propagates information that changes agent behavior. This is a Write operation with high severity because it can influence the behavior of an entire multi-agent swarm, potentially cascading across many autonomous agents.
From the tool's definition 'Share knowledge between agents' and 'share knowledge across the swarm' — the tool distributes/writes data to multiple agents in a swarm
Attacks that exploit this kind of access
Share knowledge between agents 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 Write tool in the Ruflo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ruflo MCP server in PolicyLayer and add a rule for daa_knowledge_share: 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 Ruflo. Nothing to install.
daa_knowledge_share is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the daa_knowledge_share 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_knowledge_share. 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_knowledge_share is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
daa_knowledge_share is one line of Ruflo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →