Low Risk

azure_devops_test_plan

Get a test plan by ID

How to control azure_devops_test_plan ↓

What azure_devops_test_plan does on Cursor Azure Devops

AI agents call azure_devops_test_plan to retrieve information from Cursor Azure Devops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why azure_devops_test_plan needs a policy

This tool retrieves a test plan resource by its identifier. It performs a read-only query against Azure DevOps test plan data. No modification, deletion, execution, or financial action occurs. The verb 'Get' and the retrieval-only semantics place it clearly in the Read category with low severity.

From the tool's definition Tool name includes 'get' operation pattern and description states 'Get a test plan by ID' — a retrieval operation with no side effects.

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

How to control azure_devops_test_plan

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

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

azure_devops_test_plan 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 Cursor Azure Devops — 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 azure_devops_test_plan

What does the azure_devops_test_plan tool do? +

Get a test plan by ID. It is categorised as a Read tool in the Cursor Azure Devops MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on azure_devops_test_plan? +

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

What risk level is azure_devops_test_plan? +

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

Can I rate-limit azure_devops_test_plan? +

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

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

azure_devops_test_plan is provided by the Cursor Azure Devops MCP server (maximtitovich/cursor-azure-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 Cursor Azure Devops tool call.

Start from Cursor Azure Devops, 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.

20 Cursor Azure Devops 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.