ml_detect_anomalies
Run anomaly detection on operational metrics (alert volume, incident trends, etc.)
This record as markdown: /tools/tedorigawa001-servicenow-mcp/ml-detect-anomalies.md
What ml_detect_anomalies does on ServiceNow-MCP
AI agents invoke ml_detect_anomalies to trigger actions in ServiceNow-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why ml_detect_anomalies is rated High
The tool runs a machine learning anomaly detection job against live operational metrics. This is an Execute category action as it triggers an external computation/analysis process. While it appears read-only in intent, it actively runs a model/process rather than simply retrieving stored data.
From the tool's definition 'Run anomaly detection on operational metrics' — the tool actively executes an ML/analytics process against operational data
Attacks that exploit this kind of access
The rule that runs ml_detect_anomalies safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ml_detect_anomalies, this is the rule to start with:
ml_detect_anomalies stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every ml_detect_anomalies call is checked against it from then on.
Questions about ml_detect_anomalies
Run anomaly detection on operational metrics (alert volume, incident trends, etc.). It is categorised as a Execute tool in the ServiceNow-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ServiceNow MCP server in PolicyLayer and add a rule for ml_detect_anomalies: 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 ServiceNow-MCP. Nothing to install.
ml_detect_anomalies is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ml_detect_anomalies 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 ml_detect_anomalies. 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.
ml_detect_anomalies is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow, and thousands of servers like it.
Across the catalogue