Searches the local database of Azure DevOps APIs and parameters to find the correct endpoints offline.
AI agents call api.docs to retrieve information from Azure DevOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves API documentation and endpoint information from a local database without creating, modifying, deleting, or executing any resources. It is purely informational/reference functionality, making it a Read category risk with low severity.
From the tool's definition Tool description states it 'Searches the local database' and 'find the correct endpoints offline' — this is a query/lookup operation with no data modification or execution capability.
Attacks that exploit this kind of access
Searches the local database of Azure DevOps APIs and parameters to find the correct endpoints offline. It is categorised as a Read tool in the Azure DevOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure DevOps MCP Server MCP server in PolicyLayer and add a rule for api.docs: 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.
api.docs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the api.docs 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 api.docs. 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.
api.docs is provided by the Azure DevOps MCP Server MCP server (varnierg/mcp-for-azure-devops). 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 →