AI agents call get_run_status 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 performs a data retrieval operation with no side effects. It queries the status of a robot run but does not create, modify, delete, execute commands, or trigger financial transactions. The verb 'Get' and the absence of any state-changing language clearly indicate a Read category classification.
From the tool's definition Tool name 'get_run_status' and description 'Get detailed status of a specific run' indicate a query operation that retrieves information about an existing run without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_run_status 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_run_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_run_status": {}
}
}get_run_status 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.
Get detailed status of a specific run. 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_run_status: 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_run_status 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_run_status 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_run_status. 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_run_status 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.