Low Risk

get_work_item

Get work items by IDs

How to control get_work_item ↓

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

Low Risk

This tool retrieves work item data by ID, which is a read-only operation with no side effects. It does not create, modify, delete, or execute anything—it simply queries and returns information from Azure DevOps. The blast radius of misuse is minimal (potential information disclosure of work item details).

From the tool's definition Tool name 'get_work_item' and description 'Get work items by IDs' indicate retrieval of existing data without modification. The verb 'Get' and the sibling context (list_work_items, get_boards, get_wiki_page) confirm this is a query operation.

Documented attack patterns abuse exactly the kind of access get_work_item gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Azure DevOps MCP Server for Cline, and nothing reaches the server without passing your rules. This is the rule we recommend for get_work_item:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_work_item": {}
  }
}

get_work_item 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 Azure DevOps MCP Server for Cline — 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.

Go deeper

What does the get_work_item tool do? +

Get work items by IDs. It is categorised as a Read tool in the Azure DevOps MCP Server for Cline MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_work_item? +

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

What risk level is get_work_item? +

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

Can I rate-limit get_work_item? +

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

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

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

Enforce policy on every Azure DevOps MCP Server for Cline tool call.

Deterministic rules across all 15 Azure DevOps MCP Server for Cline tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

15 Azure DevOps MCP Server for Cline tools catalogued and risk-classified — across an index of 42,500+ 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.