AI agents invoke runComplianceChecks 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 executes compliance checking logic whose effects depend on the standards and configurations passed as arguments. While not destructive or financial, it triggers external operations and workflows that could impact compliance reporting, CI/CD pipelines, or deployment gates.
From the tool's definition Tool name 'runComplianceChecks' with description 'Run compliance checks against standards' indicates execution of compliance scanning operations.
Documented attack patterns abuse exactly the kind of access runComplianceChecks 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 runComplianceChecks:
{
"version": "1",
"default": "deny",
"tools": {
"runComplianceChecks": {
"limits": [
{
"counter": "runcompliancechecks_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}runComplianceChecks 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.
Run compliance checks against standards. 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 runComplianceChecks: 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.
runComplianceChecks 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 runComplianceChecks 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 runComplianceChecks. 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.
runComplianceChecks 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.