WinCC V8 MCP Server

38 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated:

3 can modify or destroy data
35 read-only
38 tools total

Community server · catalogue entry verified 12/06/2026

How to control WinCC V8 MCP Server ↓

What WinCC V8 MCP Server exposes to your agents

Read (35) Write / Execute (3) Destructive / Financial (0)
High Risk

The most dangerous WinCC V8 MCP Server tools

3 of WinCC V8 MCP Server's 38 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control WinCC V8 MCP Server

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

Rate limit write operations
{
  "wincc-write-tag-value": {
    "limits": [
      {
        "counter": "wincc-write-tag-value_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "wincc-get-alarm-limit-value": {
    "limits": [
      {
        "counter": "wincc-get-alarm-limit-value_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register WinCC V8 MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON WINCC V8 →

Free to start. No card required.

All 38 WinCC V8 MCP Server tools

READ 35 tools
Read wincc-get-alarm-limit-value Reads limit values for a tag. GET /alarmLogging/LimitValue/{tagName}. Use Accept-Language for response languag Read wincc-get-alarm-limit-values Lists limit values. GET /alarmLogging/LimitValues with optional paging (itemLimit, continuationPoint). Use Acc Read wincc-get-alarm-message Reads a message. GET /alarmLogging/Message/{messageNumber}. Use Accept-Language for response language and Cont Read wincc-get-alarm-message-block Reads a message block. GET /alarmLogging/MessageBlock/{messageBlockName}. Use Accept-Language for response lan Read wincc-get-alarm-message-blocks Lists message blocks. GET /alarmLogging/MessageBlocks with optional paging (itemLimit, continuationPoint). Use Read wincc-get-alarm-message-class Reads a message class. GET /alarmLogging/MessageClass/{messageClassName}. Use Accept-Language for response lan Read wincc-get-alarm-message-classes Lists message classes. GET /alarmLogging/MessageClasses with optional paging (itemLimit, continuationPoint). U Read wincc-get-alarm-message-group Reads a message group. GET /alarmLogging/MessageGroup/{messageGroupName}. Use Accept-Language for response lan Read wincc-get-alarm-message-groups Lists message groups. GET /alarmLogging/MessageGroups with optional paging (itemLimit, continuationPoint). Use Read wincc-get-alarm-message-type Reads a message type. GET /alarmLogging/MessageType/{messageTypeName}. Use Accept-Language for response langua Read wincc-get-alarm-message-types Lists message types. GET /alarmLogging/MessageTypes with optional paging (itemLimit, continuationPoint). Use A Read wincc-get-alarm-messages Lists messages. GET /alarmLogging/Messages with optional paging (itemLimit, continuationPoint). Use Accept-Lan Read wincc-get-alarm-rest-filter Reads a REST filter. GET /alarmLogging/RestFilter/{filterName}. Use Accept-Language for response language and Read wincc-get-alarm-rest-filters Lists configured REST filters. GET /alarmLogging/RestFilters. Use Accept-Language for response language and Co Read wincc-get-archive Read configuration data of a specific process value archive Read wincc-get-archive-tag Read configuration data of an archive system tag Read wincc-get-archive-tags Read configuration data of all archive system tags Read wincc-get-archive-value Read runtime value of an archive variable Read wincc-get-archive-values Read runtime values of multiple archive variables Read wincc-get-archive-variable Read configuration data of a specific archive variable Read wincc-get-archive-variables Read configuration data of all variables in an archive Read wincc-get-archives Read configuration data of all process value archives Read wincc-get-connection Read configuration data of a specific connection Read wincc-get-connections Reads configuration data of all connections in Tag Management. Base URL: /tagManagement. Endpoint: Connections Read wincc-get-group Read configuration data of a specific tag group Read wincc-get-groups Read configuration data of all tag groups Read wincc-get-structure-type Read configuration data of a specific structure type Read wincc-get-structure-types Read configuration data of all structure types Read wincc-get-structure-variables Read instances of structure types Read wincc-get-tag-config Read configuration data of a specific tag Read wincc-get-tag-value Read runtime value of a specific tag Read wincc-get-tag-values Read runtime values of multiple tags Read wincc-get-tags-config Read configuration data of all tags Read wincc-get-timer Read configuration data of a specific archive system timer Read wincc-get-timers Read configuration data of all archive system timers

Questions about WinCC V8 MCP Server

How do I prevent bulk modifications through WinCC V8 MCP Server? +

The WinCC V8 MCP Server server has 2 write tools including wincc-write-tag-value, wincc-write-tag-values. 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 WinCC V8 MCP Server.

How many tools does the WinCC V8 MCP Server MCP server expose? +

38 tools across 2 categories: Read, Write. 35 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on WinCC V8 MCP Server? +

Register the WinCC V8 MCP Server 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 WinCC V8 MCP Server tool call.

Deterministic rules across all 38 WinCC V8 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

38 WinCC V8 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.