ado_upload_attachment · Mcp Azure MCP: Risk & Policy

WHAT IT DOES

What ado_upload_attachment does on Mcp Azure

AI agents use ado_upload_attachment to create or update resources in Mcp Azure — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Azure environment.

WHY IT NEEDS A POLICY

Why ado_upload_attachment needs a policy

This tool creates a new attachment record in Azure DevOps, which is a reversible write operation. It does not execute code, delete data, or move funds. The medium severity reflects that malicious uploads could introduce unwanted attachments (e.g., malware, sensitive data) into DevOps work items, but the effect is limited to the attachment itself and can be removed.

From the tool's definition ado_upload_attachment: 'Sube un archivo como adjunto a Azure DevOps y devuelve la URL del adjunto' (uploads a file as an attachment to Azure DevOps and returns the attachment URL). This is a create operation that adds new data to the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ado_upload_attachment Rate-limited

ado_upload_attachment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ado_upload_attachment": {
      "limits": [
        {
          "counter": "ado_upload_attachment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about ado_upload_attachment

What does the ado_upload_attachment tool do? +

Sube un archivo como adjunto a Azure DevOps y devuelve la URL del adjunto. It is categorised as a Write tool in the Mcp Azure MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ado_upload_attachment? +

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

What risk level is ado_upload_attachment? +

ado_upload_attachment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ado_upload_attachment? +

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

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

ado_upload_attachment is provided by the Mcp Azure MCP server (soulberto/mcp-azure). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.