x_federation_channel_create
Create a swarm channel. visibility=public gives a named stream every relay member can read (pub:<name>). visibility=private generates a 32-byte key HERE, stores it at ~/.ruflo/channels.json (0600), and returns an opaque id (prv:<hex>) that leaks neither the name nor the topic. Use when a stream o...
This record as markdown: /tools/ruflo/x-federation-channel-create.md
What x_federation_channel_create does on Ruflo
AI agents use x_federation_channel_create 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.
Why x_federation_channel_create is rated Medium
Creates persistent channel configuration with cryptographic keys; reversible but security-critical for swarm infrastructure.
From the tool's definition Create a swarm channel, stores key at ~/.ruflo/channels.json, returns opaque id
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs x_federation_channel_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x_federation_channel_create, this is the rule to start with:
x_federation_channel_create 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 Ruflo, apply this rule, and every x_federation_channel_create call is checked against it from then on.
Questions about x_federation_channel_create
Create a swarm channel. visibility=public gives a named stream every relay member can read (pub:<name>). visibility=private generates a 32-byte key HERE, stores it at ~/.ruflo/channels.json (0600), and returns an opaque id (prv:<hex>) that leaks neither the name nor the topic. Use when a stream of work should be separated from the shared firehose, or kept unreadable by the relay and the gateway. Creating a private channel and then expecting the gateway to read it is wrong: the gateway holds no channel key and cannot decrypt (ADR-386). Losing the key file loses the channel. 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 x_federation_channel_create: 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.
x_federation_channel_create 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 x_federation_channel_create 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 x_federation_channel_create. 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.
x_federation_channel_create 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.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue