federation_bbs_publish
agentbbs — Publish a domain event from a pod agent to a BBS room (ADR-164 Phase 1). Wraps the payload in a ReplicateMessage envelope (envelopeId, seq, ts, msgType, payload) and appends it to the room log. Use when an agent has produced a typed event (pod-status, task-result, alert, human-override...
This record as markdown: /tools/io-github-ruvnet-claude-flow/federation-bbs-publish.md
What federation_bbs_publish does on Claude Flow
AI agents use federation_bbs_publish 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 federation_bbs_publish is rated Medium
This tool creates and modifies structured event records in a distributed system (agent-to-room publication). While it enforces architectural constraints (budget caps, PII gating, sequencing), it is fundamentally a Write operation: it persists new data to a shared log. It is not Destructive because appending is reversible and doesn't purge data.
From the tool's definition The tool 'federation_bbs_publish' appends messages to a room log with 'envelopeId, seq, ts, msgType, payload' metadata, explicitly stating it 'appends it to the room log' and enforces 'monotonic seq numbering.' This is data modification that is reversible…
Attacks that exploit this kind of access
The rule that runs federation_bbs_publish 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 federation_bbs_publish, this is the rule to start with:
federation_bbs_publish 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every federation_bbs_publish call is checked against it from then on.
Questions about federation_bbs_publish
agentbbs — Publish a domain event from a pod agent to a BBS room (ADR-164 Phase 1). Wraps the payload in a ReplicateMessage envelope (envelopeId, seq, ts, msgType, payload) and appends it to the room log. Use when an agent has produced a typed event (pod-status, task-result, alert, human-override-ack, bench-result) that the human cockpit or other pods need to see. Storing into raw memory_store is wrong because it skips the room-scoped budget cap, PII pipeline gating, and monotonic seq numbering that ADR-164 §3.2.2 requires. Optional dep — degrades to {degraded:true} when missing. 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.
Register the Claude Flow MCP server in PolicyLayer and add a rule for federation_bbs_publish: 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.
federation_bbs_publish 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 federation_bbs_publish 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 federation_bbs_publish. 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.
federation_bbs_publish 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.
This server
Across the catalogue