beacons_updateDashboardResource
Replace the given fields of one configuration record (PATCH /v1/beacons/dashboard/fleets/{fleet_id}/resources/{family}/{resource_id})
This record as markdown: /tools/onesi-genesis-mcp/beacons-updatedashboardresource.md
What beacons_updateDashboardResource does on Genesis
AI agents use beacons_updateDashboardResource 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 |
|---|---|---|---|
body | object | Yes | |
family | string | Yes | Configuration record family. |
fleet_id | string | Yes | Actual nonzero canonical lowercase fleet UUID; the receiver verifies ownership in the current selection. |
resource_id | string | Yes | Nonzero lowercase record UUID returned by create or list. |
Parameters from the server's own tool schema.
Why beacons_updateDashboardResource is rated Medium
An AI agent can call beacons_updateDashboardResource 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
The rule that runs beacons_updateDashboardResource 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_updateDashboardResource, this is the rule to start with:
beacons_updateDashboardResource 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 Genesis, apply this rule, and every beacons_updateDashboardResource call is checked against it from then on.
Questions about beacons_updateDashboardResource
Replace the given fields of one configuration record (PATCH /v1/beacons/dashboard/fleets/{fleet_id}/resources/{family}/{resource_id}). 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.
beacons_updateDashboardResource accepts 4 parameters: body, family, fleet_id, resource_id. Required: body, family, fleet_id, resource_id. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for beacons_updateDashboardResource: 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.
beacons_updateDashboardResource 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 beacons_updateDashboardResource 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 beacons_updateDashboardResource. 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.
beacons_updateDashboardResource 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.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue