AI agents use set_ado_organization to create or update resources in Ado — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ado environment.
This is a Write action because it modifies server configuration state (the active organization context). While it doesn't create data objects in the traditional sense, it changes operational state that affects all downstream tool behavior.
From the tool's definition The tool description states it 'Switches the active Azure DevOps organization for the MCP server.' This modifies server-side state by changing which organization is in scope, affecting subsequent operations.
Attacks that exploit this kind of access
Switches the active Azure DevOps organization for the MCP server. It is categorised as a Write tool in the Ado MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ado MCP server in PolicyLayer and add a rule for set_ado_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 Ado. Nothing to install.
set_ado_organization is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_ado_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.
Set action: deny in the PolicyLayer policy for set_ado_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.
set_ado_organization is provided by the Ado MCP server (raboley/ado-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →