Execute a single ATF test (requires ATF_ENABLED=true)
AI agents invoke run_atf_test 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.
This tool executes automated tests, which is a code execution operation. The outcome depends on the test's logic and can have side effects on the ServiceNow instance (creating/modifying/deleting data, triggering workflows, etc.). While not inherently destructive by design, ATF tests can be configured to perform any operation, making this an Execute risk.
From the tool's definition Tool name and description: 'run_atf_test' with 'Execute a single ATF test'. ATF refers to ServiceNow's Automated Test Framework, which runs test suites that can perform arbitrary operations against the ServiceNow instance.
Attacks that exploit this kind of access
Execute a single ATF test (requires ATF_ENABLED=true). 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 run_atf_test: 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.
run_atf_test 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 run_atf_test 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 run_atf_test. 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.
run_atf_test 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →