Test Azure DevOps Personal Access Token (PAT) validity and permissions. Helps diagnose PAT-related authentication failures.
AI agents call test_azure_devops_pat to retrieve information from Bc Code Intelligence without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool tests/validates a PAT token by querying Azure DevOps to check its validity and permissions. It is a read/diagnostic operation with no side effects. However, it involves handling authentication credentials (PAT), which carries medium severity risk since misuse could expose or leak sensitive tokens.
From the tool's definition Test Azure DevOps Personal Access Token (PAT) validity and permissions. Helps diagnose PAT-related authentication failures.
Documented attack patterns abuse exactly the kind of access test_azure_devops_pat gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bc Code Intelligence, and nothing reaches the server without passing your rules. This is the rule we recommend for test_azure_devops_pat:
{
"version": "1",
"default": "deny",
"tools": {
"test_azure_devops_pat": {}
}
} test_azure_devops_pat is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Test Azure DevOps Personal Access Token (PAT) validity and permissions. Helps diagnose PAT-related authentication failures. It is categorised as a Read tool in the Bc Code Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Bc Code Intelligence MCP server in PolicyLayer and add a rule for test_azure_devops_pat: 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 Bc Code Intelligence. Nothing to install.
test_azure_devops_pat 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 test_azure_devops_pat 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 test_azure_devops_pat. 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.
test_azure_devops_pat is provided by the Bc Code Intelligence MCP server (jeremyvyska/bc-code-intelligence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bc Code Intelligence, 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.
27 Bc Code Intelligence tools catalogued and risk-classified — across an index of 43,000+ MCP servers.