Optimize test suite execution for faster feedback
AI agents invoke runTestOptimization 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 runs test optimization operations which constitute code execution and triggering of external test infrastructure. The effects depend on the test suite configuration and arguments provided, making it an Execute category risk. Severity is high because misconfigured or maliciously-directed test optimization could consume significant resources, introduce test coverage gaps, or execute unintended test code.
From the tool's definition Tool name 'runTestOptimization' and description 'Optimize test suite execution for faster feedback' indicates triggering external operations that execute tests and modify test execution behavior.
Documented attack patterns abuse exactly the kind of access runTestOptimization 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 runTestOptimization:
{
"version": "1",
"default": "deny",
"tools": {
"runTestOptimization": {
"limits": [
{
"counter": "runtestoptimization_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}runTestOptimization 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.
Optimize test suite execution for faster feedback. 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 runTestOptimization: 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.
runTestOptimization 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 runTestOptimization 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 runTestOptimization. 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.
runTestOptimization 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.