AI agents call get_method_run to retrieve information from Wago Plc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the status of an asynchronous method execution that was previously initiated. Polling for status is a read operation that queries existing state without creating, modifying, deleting, or executing anything. While the parent server involves PLCs and method invocation, this specific tool is purely observational - it returns status information about a method that is already running elsewhere.
From the tool's definition Tool is described as 'Poll an async method run' and 'check status' - these are query/retrieval operations with no side effects. The word 'Poll' and 'check status' indicate reading operation state rather than modifying it.
Attacks that exploit this kind of access
Poll an async method run. Use after invoke_method(wait=False) to check status. It is categorised as a Read tool in the Wago Plc MCP Server, which means it retrieves data without modifying state.
Register the Wago Plc MCP server in PolicyLayer and add a rule for get_method_run: 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 Wago Plc. Nothing to install.
get_method_run 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_method_run 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_method_run. 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_method_run is provided by the Wago Plc MCP server (wagoalex/wago-plc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →