Upload a protocol file to an Opentrons robot
AI agents use upload_protocol to create or update resources in Opentrons MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Opentrons MCP Server environment.
Uploading a protocol file creates or modifies executable instructions on lab automation hardware. While not destructive (the upload is reversible via deletion or overwrite), it is a Write action that configures robot behavior.
From the tool's definition Tool uploads a protocol file to an Opentrons robot, which modifies robot state and configuration but does not irreversibly delete data. The description explicitly states 'Upload a protocol file', indicating file creation/modification on the robot.
Documented attack patterns abuse exactly the kind of access upload_protocol gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Opentrons MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for upload_protocol:
{
"version": "1",
"default": "deny",
"tools": {
"upload_protocol": {
"limits": [
{
"counter": "upload_protocol_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} upload_protocol 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.
Free to start. No card required.
Upload a protocol file to an Opentrons robot. It is categorised as a Write tool in the Opentrons MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Opentrons MCP Server MCP server in PolicyLayer and add a rule for upload_protocol: 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 Opentrons MCP Server. Nothing to install.
upload_protocol 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_protocol 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_protocol. 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_protocol is provided by the Opentrons MCP Server MCP server (yerbymatey/opentrons-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Opentrons MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Opentrons MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.