beacons_updateBridgeDevice

Update bridge device (name, nicknames) (PATCH /v1/beacons/bridge/devices/{id}) [service status: unverified]

SERVERGenesis SOURCE@lifesi/genesis-mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lifesi-genesis-mcp/beacons-updatebridgedevice.md

WHAT IT DOES

What beacons_updateBridgeDevice does on Genesis

AI agents use beacons_updateBridgeDevice to create or update resources in Genesis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Genesis environment.

Parameter	Type	Required	Description
`id`	string	Yes	Device ID
`body`	object	Yes

Parameters from the server's own tool schema.

RISK

Why beacons_updateBridgeDevice is rated Medium

An AI agent can call beacons_updateBridgeDevice faster than any human can review: one bad instruction and it creates or modifies resources in Genesis by the hundred, each call as confident as the last.

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs beacons_updateBridgeDevice 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_updateBridgeDevice, this is the rule to start with:

beacons_updateBridgeDevice Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "beacons_updateBridgeDevice": {
      "limits": [
        {
          "counter": "beacons_updatebridgedevice_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about beacons_updateBridgeDevice

What does the beacons_updateBridgeDevice tool do? +

Update bridge device (name, nicknames) (PATCH /v1/beacons/bridge/devices/{id}) [service status: unverified]. It is categorised as a Write tool in the Genesis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does beacons_updateBridgeDevice accept? +

beacons_updateBridgeDevice accepts 2 parameters: id, body. Required: id, body. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on beacons_updateBridgeDevice? +

Register the Genesis MCP server in PolicyLayer and add a rule for beacons_updateBridgeDevice: 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_updateBridgeDevice? +

beacons_updateBridgeDevice is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit beacons_updateBridgeDevice? +

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

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

beacons_updateBridgeDevice is provided by the Genesis MCP server (@lifesi/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 252 Genesis tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →