AI agents call wincc-get-tag-values to retrieve information from WinCC V8 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves current values from SCADA tags, which is a read-only query operation. Even in a critical infrastructure context (SCADA), reading tag values does not modify state, execute commands, or trigger physical actions. The blast radius is minimal—an agent using this tool gains visibility into system state but cannot change configuration, delete data, or cause destructive operations.
From the tool's definition Tool name 'wincc-get-tag-values' and description 'Read runtime values of multiple tags' explicitly indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access wincc-get-tag-values gives an agent:
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. This is the rule we recommend for wincc-get-tag-values:
{
"version": "1",
"default": "deny",
"tools": {
"wincc-get-tag-values": {}
}
} wincc-get-tag-values 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.
Read runtime values of multiple tags. It is categorised as a Read tool in the WinCC V8 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WinCC V8 MCP Server MCP server in PolicyLayer and add a rule for wincc-get-tag-values: 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 WinCC V8 MCP Server. Nothing to install.
wincc-get-tag-values 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 wincc-get-tag-values 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 wincc-get-tag-values. 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.
wincc-get-tag-values is provided by the WinCC V8 MCP Server MCP server (vogler75/winccv8-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WinCC V8 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.
38 WinCC V8 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.