Retrieves historical tag values from the database for the specified tags or logging tags.
AI agents call get-logged-tag-values to retrieve information from WinCC Unified MCP XT without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical data from a SCADA system database without modifying, executing, or destroying data. While SCADA systems manage critical infrastructure, this specific tool is read-only.
From the tool's definition Tool name contains 'get' and description states 'Retrieves historical tag values from the database'; no modification, deletion, or execution is performed. The word 'Retrieves' indicates a read-only operation.
Documented attack patterns abuse exactly the kind of access get-logged-tag-values gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WinCC Unified MCP XT, and nothing reaches the server without passing your rules. This is the rule we recommend for get-logged-tag-values:
{
"version": "1",
"default": "deny",
"tools": {
"get-logged-tag-values": {}
}
} get-logged-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.
Retrieves historical tag values from the database for the specified tags or logging tags. It is categorised as a Read tool in the WinCC Unified MCP XT MCP Server, which means it retrieves data without modifying state.
Register the WinCC Unified MCP XT MCP server in PolicyLayer and add a rule for get-logged-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 Unified MCP XT. Nothing to install.
get-logged-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 get-logged-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 get-logged-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.
get-logged-tag-values is provided by the WinCC Unified MCP XT MCP server (mrwan84/wincc-unified-mcp-xt). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WinCC Unified MCP XT, 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.
9 WinCC Unified MCP XT tools catalogued and risk-classified — across an index of 43,000+ MCP servers.