AI agents call get_runs to retrieve information from Opentrons MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical or current run data from the robot's system without altering state, executing protocols, or causing physical actions. It is a passive information query, consistent with the Read category. While the Opentrons server has destructive capabilities (robot control, protocol execution), this specific tool only lists existing runs.
From the tool's definition Tool name 'get_runs' and description 'List all runs on the robot' indicate a query/retrieval operation with no modification or execution of robot actions.
Documented attack patterns abuse exactly the kind of access get_runs 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 get_runs:
{
"version": "1",
"default": "deny",
"tools": {
"get_runs": {}
}
}get_runs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all runs on the robot. It is categorised as a Read tool in the Opentrons MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Opentrons MCP Server MCP server in PolicyLayer and add a rule for get_runs: 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.
get_runs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_runs 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 get_runs. 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.
get_runs 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.