federation_wg_keyrotate

ADR-111 Phase 6: rotate the local WG keypair. Returns the new public key + recommended next steps (republish manifest, peers regenerate their wg-quick config, grace-period destruction of old key). DESTRUCTIVE — the old private key is overwritten on disk; existing tunnels are dropped until peers u...

Server Ruflo ruvnet/ruflo
Category Destructive
Risk class Critical
Parameters 00 required

What federation_wg_keyrotate does on Ruflo

AI agents call federation_wg_keyrotate to permanently remove resources in Ruflo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why federation_wg_keyrotate needs a policy

The tool irreversibly overwrites the existing WireGuard private key on disk and drops all active tunnels. The old key cannot be recovered once overwritten, making this a clearly destructive operation.

From the tool's definition DESTRUCTIVE — the old private key is overwritten on disk; existing tunnels are dropped until peers update

Questions about federation_wg_keyrotate

What does the federation_wg_keyrotate tool do? +

ADR-111 Phase 6: rotate the local WG keypair. Returns the new public key + recommended next steps (republish manifest, peers regenerate their wg-quick config, grace-period destruction of old key). DESTRUCTIVE — the old private key is overwritten on disk; existing tunnels are dropped until peers update. It is categorised as a Destructive tool in the Ruflo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on federation_wg_keyrotate? +

Register the Ruflo MCP server in PolicyLayer and add a rule for federation_wg_keyrotate: 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.

What risk level is federation_wg_keyrotate? +

federation_wg_keyrotate is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit federation_wg_keyrotate? +

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

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

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

// THE FULL RECORD

federation_wg_keyrotate 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.