AI agents invoke runAutomatedTests to trigger actions in Azure Devops. 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 triggers execution of automated test suites, which runs code whose side effects depend on the test suite logic and environment. While typically non-destructive, test execution can have broad effects (database modifications, external API calls, resource consumption), making it an Execute-category tool.
From the tool's definition Tool name 'runAutomatedTests' combined with description 'Execute automated test suites' explicitly indicates execution of external operations (test suites). The verb 'Execute' in the description is definitive.
Documented attack patterns abuse exactly the kind of access runAutomatedTests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure Devops, and nothing reaches the server without passing your rules. This is the rule we recommend for runAutomatedTests:
{
"version": "1",
"default": "deny",
"tools": {
"runAutomatedTests": {
"limits": [
{
"counter": "runautomatedtests_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}runAutomatedTests 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.
Free to start. No card required.
Execute automated test suites. It is categorised as a Execute tool in the Azure Devops MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Azure Devops MCP server in PolicyLayer and add a rule for runAutomatedTests: 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 Azure Devops. Nothing to install.
runAutomatedTests 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 runAutomatedTests 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 runAutomatedTests. 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.
runAutomatedTests is provided by the Azure Devops MCP server (ryancardin15/azuredevops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 97 Azure Devops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
97 Azure Devops tools catalogued and risk-classified — across an index of 42,500+ MCP servers.