// SCAN REPORT

Wago Plc

14 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 2 Jul 2026

4 can modify or destroy data

10 read-only

14 tools total

Community server · catalogue entry verified 02/07/2026

How to control Wago Plc ↓

TOOL MAP

What Wago Plc exposes to your agents

Read (10) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Wago Plc tools

Destructive · High delete_watchlist This tool irreversibly deletes data (a watchlist) from the PLC monitoring system. Execute · Critical invoke_method This tool invokes arbitrary methods on WAGO PLCs with caller-supplied arguments. Write · Medium create_watchlist This tool creates persistent server-side state (a watchlist) for parameter monitoring. Write · High set_parameters This tool creates or modifies data reversibly via a PATCH call to set PLC parameters.

4 of Wago Plc's 14 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Wago Plc

PolicyLayer is an MCP gateway — it sits between your AI agents and Wago Plc, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_watchlist": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_watchlist": {
    "limits": [
      {
        "counter": "create_watchlist_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "describe_plc": {
    "limits": [
      {
        "counter": "describe_plc_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Wago Plc — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON WAGO PLC →

Instant setup, no code required.

FULL CATALOGUE

All 14 Wago Plc tools

DESTRUCTIVE 1 tools

Destructive delete_watchlist Delete a watchlist to free server resources before timeout.

EXECUTE 1 tools

Execute invoke_method Invoke a method. Pass arguments as a flat dict {name: value}.

WRITE 2 tools

Write create_watchlist Create a server-side watchlist of parameters for efficient repeated polling. Write set_parameters Write multiple parameters in one PATCH call. Pre-validates writeability from cache.

READ 10 tools

Read describe_plc Get capability summary for a PLC: counts + feature names. Cheap, cached. Read find_methods Search method IDs by substring/fuzzy match. Returns up to limit matches (default 20). Read find_parameters find_parameters Read get_method Get method metadata with inline inArgs/outArgs signatures. One call gives the full schema needed for invoke_me Read get_method_run Poll an async method run. Use after invoke_method(wait=False) to check status. Read get_parameter Read a single parameter value. Resolves enum values to human-readable labels. Read get_parameters_bulk get_parameters_bulk Read get_plc_audit_log get_plc_audit_log Read list_plcs List all reachable WAGO PLCs. Use first to find a target IP. Read read_watchlist Read current values from an existing watchlist. Resets the timeout.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Wago Plc

Can an AI agent delete data through the Wago Plc MCP server? +

Yes. The Wago Plc server exposes 1 destructive tools including delete_watchlist. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Wago Plc? +

The Wago Plc server has 2 write tools including create_watchlist, set_parameters. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Wago Plc.

How many tools does the Wago Plc MCP server expose? +

14 tools across 4 categories: Destructive, Execute, Read, Write. 10 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Wago Plc? +

Register the Wago Plc MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Wago Plc tool call.

Deterministic rules across all 14 Wago Plc tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON WAGO PLC →

Instant setup, no code required.

14 Wago Plc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.