Retrieves active alarms from the specified systems.
AI agents call get-active-alarms 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 performs data retrieval only—it fetches active alarms from SCADA systems without side effects. However, the severity is elevated to 'medium' because SCADA alarm data can be operationally sensitive; misuse (e.g., an agent repeatedly fetching alarms to trigger noisy alerts or reconnaissance) could disrupt monitoring or reveal system state to an attacker.
From the tool's definition The tool name 'get-active-alarms' and description 'Retrieves active alarms' indicate a read-only operation that queries alarm state without modification.
Documented attack patterns abuse exactly the kind of access get-active-alarms 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-active-alarms:
{
"version": "1",
"default": "deny",
"tools": {
"get-active-alarms": {}
}
} get-active-alarms 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 active alarms from the specified systems. 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-active-alarms: 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-active-alarms 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-active-alarms 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-active-alarms. 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-active-alarms 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.