api.call · Azure DevOps MCP Server MCP: Risk & Policy

WHAT IT DOES

What api.call does on Azure DevOps MCP Server

AI agents invoke api.call to trigger actions in Azure DevOps MCP Server. 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 IT NEEDS A POLICY

Why api.call needs a policy

This tool can execute arbitrary REST API calls against ALL Azure DevOps endpoints, meaning it can perform reads, writes, deletions, pipeline triggers, repository modifications, and more depending on the arguments passed. Since it spans multiple categories, the most severe applicable is chosen.

From the tool's definition "Executes a generic Azure DevOps REST API call. Supports ALL DevOps endpoints."

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

api.call Rate-limited

api.call 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "api.call": {
      "limits": [
        {
          "counter": "api.call_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Azure DevOps MCP Server, so you can run agents against it safely.

FAQ

Questions about api.call

What does the api.call tool do? +

Executes a generic Azure DevOps REST API call. Supports ALL DevOps endpoints. (Default API Version: 7.1). It is categorised as a Execute tool in the Azure DevOps MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on api.call? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for api.call: 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 MCP Server. Nothing to install.

What risk level is api.call? +

api.call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit api.call? +

Yes. Add a rate_limit block to the api.call 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.

How do I block api.call completely? +

Set action: deny in the PolicyLayer policy for api.call. 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.

What MCP server provides api.call? +

api.call is provided by the Azure DevOps MCP Server MCP server (varnierg/mcp-for-azure-devops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.