Upload devices.json (device routing overrides) to the active preset slot.
AI agents use upload_devices_overrides to create or update resources in Electra One — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Electra One environment.
The tool creates or modifies preset configuration data (device routing overrides) in a reversible manner. It does not delete data (would be Destructive) or execute arbitrary code (Execute). The 'active preset slot' context suggests the changes can be overwritten or reverted by uploading different configuration.
From the tool's definition Tool description states 'Upload devices.json (device routing overrides) to the active preset slot' — this modifies configuration data in the active preset.
Attacks that exploit this kind of access
Upload devices.json (device routing overrides) to the active preset slot. It is categorised as a Write tool in the Electra One MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Electra One MCP server in PolicyLayer and add a rule for upload_devices_overrides: 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 Electra One. Nothing to install.
upload_devices_overrides 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 upload_devices_overrides 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 upload_devices_overrides. 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.
upload_devices_overrides is provided by the Electra One MCP server (roomi-fields/electra-one-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →