upload_persisted_data · Electra One MCP: Risk & Policy

WHAT IT DOES

What upload_persisted_data does on Electra One

AI agents use upload_persisted_data 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.

WHY IT NEEDS A POLICY

Why upload_persisted_data needs a policy

This tool creates or modifies preset configuration data on the Electra One device. It is Write rather than Destructive because it updates data in a reversible manner (data can be overwritten or reverted). It is not Execute because it is not running code or triggering operations with argument-dependent effects—it is simply transferring a specific data file.

From the tool's definition upload_persisted_data uploads data.json to the active preset slot; the description explicitly states it uploads data to modify the preset.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_persisted_data Rate-limited

upload_persisted_data 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": {
    "upload_persisted_data": {
      "limits": [
        {
          "counter": "upload_persisted_data_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Electra One, so you can run agents against it safely.

FAQ

Questions about upload_persisted_data

What does the upload_persisted_data tool do? +

Upload data.json (Lua persist() table) 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.

How do I enforce a policy on upload_persisted_data? +

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

What risk level is upload_persisted_data? +

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

Can I rate-limit upload_persisted_data? +

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

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

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