beacons_getDashboardPeerWireguardConfig

Read one peer's WireGuard tunnel configuration (GET /v1/beacons/dashboard/fleets/{fleet_id}/peers/{peer_id}/wireguard-config)

SERVERGenesis SOURCE@onesi/genesis-mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/onesi-genesis-mcp/beacons-getdashboardpeerwireguardconfig.md

WHAT IT DOES

What beacons_getDashboardPeerWireguardConfig does on Genesis

AI agents call beacons_getDashboardPeerWireguardConfig to retrieve information from Genesis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`peer_id`	string	Yes	Nonzero lowercase peer UUID (the device id from the peer list).
`fleet_id`	string	Yes	Actual nonzero canonical lowercase fleet UUID; the receiver verifies ownership in the current selection.

Parameters from the server's own tool schema.

RISK

Why beacons_getDashboardPeerWireguardConfig is rated Low

Even though beacons_getDashboardPeerWireguardConfig only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs beacons_getDashboardPeerWireguardConfig safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For beacons_getDashboardPeerWireguardConfig, this is the rule to start with:

beacons_getDashboardPeerWireguardConfig Allowed

beacons_getDashboardPeerWireguardConfig is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "beacons_getDashboardPeerWireguardConfig": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every beacons_getDashboardPeerWireguardConfig call is checked against it from then on.

FAQ

Questions about beacons_getDashboardPeerWireguardConfig

What does the beacons_getDashboardPeerWireguardConfig tool do? +

Read one peer's WireGuard tunnel configuration (GET /v1/beacons/dashboard/fleets/{fleet_id}/peers/{peer_id}/wireguard-config). It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.

What parameters does beacons_getDashboardPeerWireguardConfig accept? +

beacons_getDashboardPeerWireguardConfig accepts 2 parameters: peer_id, fleet_id. Required: peer_id, fleet_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on beacons_getDashboardPeerWireguardConfig? +

Register the Genesis MCP server in PolicyLayer and add a rule for beacons_getDashboardPeerWireguardConfig: 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 Genesis. Nothing to install.

What risk level is beacons_getDashboardPeerWireguardConfig? +

beacons_getDashboardPeerWireguardConfig is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit beacons_getDashboardPeerWireguardConfig? +

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

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

beacons_getDashboardPeerWireguardConfig is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Genesis, and thousands of servers like it.

This server

All 1127 Genesis tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →