AI agents call get_process_details to retrieve information from Ado without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly suggests a read-only query operation that retrieves information about processes or configurations. Without a description, confidence is moderate (0.72), but the tool's position among other read/retrieve tools in the ADO server and absence of mutation keywords (create, delete, update) support the Read classification.
From the tool's definition Tool name 'get_process_details' uses the verb 'get', which is a retrieval operation. No description provided, but naming convention and context within an Azure DevOps MCP server (alongside tools like analyze_pipeline_input, extract_pipeline_run_data) indicate…
Attacks that exploit this kind of access
get_process_details. It is categorised as a Read tool in the Ado MCP Server, which means it retrieves data without modifying state.
Register the Ado MCP server in PolicyLayer and add a rule for get_process_details: 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.
get_process_details 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 get_process_details 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 get_process_details. 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.
get_process_details 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 →