upload_performance · Electra One MCP: Risk & Policy

WHAT IT DOES

What upload_performance does on Electra One

AI agents use upload_performance 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_performance needs a policy

This tool creates or modifies data on the Electra One device by writing a performance configuration file to an active preset slot. While reversible (presets can be overwritten or cleared using sibling tools like clear_preset_slot), the upload action itself is a Write operation that persistently changes device state.

From the tool's definition Tool uploads a performance.json file to a preset slot on the Electra One device, modifying the device's stored preset configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_performance Rate-limited

upload_performance 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_performance": {
      "limits": [
        {
          "counter": "upload_performance_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_performance

What does the upload_performance tool do? +

Upload performance.json 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_performance? +

Register the Electra One MCP server in PolicyLayer and add a rule for upload_performance: 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_performance? +

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

Can I rate-limit upload_performance? +

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

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

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

// THE FULL RECORD

upload_performance is one line of Electra One's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →