set_organization · Azure DevOps MCP Server MCP

WHAT IT DOES

What set_organization does on Azure DevOps MCP Server

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

WHY IT NEEDS A POLICY

Why set_organization needs a policy

This tool changes the active organization context for all subsequent commands. It modifies session/configuration state (a reversible Write operation), but carries medium severity because switching organizations could redirect AI agent actions to unintended Azure DevOps organizations, potentially causing misuse of resources or unauthorized access to other organizations' data.

From the tool's definition Switch to a different Azure DevOps organization for subsequent commands

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_organization Rate-limited

set_organization 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": {
    "set_organization": {
      "limits": [
        {
          "counter": "set_organization_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 Azure DevOps MCP Server, so you can run agents against it safely.

FAQ

Questions about set_organization

What does the set_organization tool do? +

Switch to a different Azure DevOps organization for subsequent commands. It is categorised as a Write tool in the Azure DevOps MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_organization? +

Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for set_organization: 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 set_organization? +

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

Can I rate-limit set_organization? +

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

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

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

// THE FULL RECORD

set_organization is one line of Azure DevOps MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →