Low Risk

get-builds

Get build definitions and recent builds

How to control get-builds ↓

What get-builds does on DevOps Enhanced MCP

AI agents call get-builds to retrieve information from DevOps Enhanced MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get-builds needs a policy

This tool retrieves information about build definitions and recent builds from Azure DevOps. It performs a read-only query operation that returns data without creating, modifying, deleting, or executing any operations. The description explicitly uses 'Get', which is a read operation. No side effects or state changes occur from calling this tool.

From the tool's definition Tool name 'get-builds' and description 'Get build definitions and recent builds' indicate a retrieval operation with no modification or execution capabilities.

Documented attack patterns abuse exactly the kind of access get-builds gives an agent:

How to control get-builds

PolicyLayer is an MCP gateway — it sits between your AI agents and DevOps Enhanced MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get-builds:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-builds": {}
  }
}

get-builds is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register DevOps Enhanced MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get-builds

What does the get-builds tool do? +

Get build definitions and recent builds. It is categorised as a Read tool in the DevOps Enhanced MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-builds? +

Register the DevOps Enhanced MCP server in PolicyLayer and add a rule for get-builds: 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 DevOps Enhanced MCP. Nothing to install.

What risk level is get-builds? +

get-builds is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-builds? +

Yes. Add a rate_limit block to the get-builds 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 get-builds completely? +

Set action: deny in the PolicyLayer policy for get-builds. 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 get-builds? +

get-builds is provided by the DevOps Enhanced MCP server (wangkanai/devops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DevOps Enhanced MCP tool call.

Start from DevOps Enhanced MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

10 DevOps Enhanced MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.