AI agents use create_watchlist to create or update resources in Wago Plc — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wago Plc environment.
This tool creates persistent server-side state (a watchlist) for parameter monitoring. It is a Write operation because it creates/configures new resources reversibly. Severity is medium because while watchlist creation is reversible and doesn't directly control critical PLC operations or delete data, it modifies server state and could interfere with monitoring if misconfigured by an agent.
From the tool's definition create_watchlist: 'Create a server-side watchlist of parameters' — this creates new configuration on the PLC server side.
Attacks that exploit this kind of access
Create a server-side watchlist of parameters for efficient repeated polling. It is categorised as a Write tool in the Wago Plc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wago Plc MCP server in PolicyLayer and add a rule for create_watchlist: 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.
create_watchlist 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 create_watchlist 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 create_watchlist. 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.
create_watchlist 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 →