Run accessibility tests on a URL and return detailed violation reports. [${configNote}]
AI agents call analyze_url to retrieve information from Accessibility Testing MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a website's accessibility status and provides analysis results. It performs no side effects, does not execute code on the target system, does not modify data, and does not create financial obligations. It is purely informational analysis comparable to a search or fetch operation.
From the tool's definition Tool runs accessibility tests on a URL and returns violation reports with no modification, deletion, or execution of commands. The description indicates data retrieval only ('return detailed violation reports').
Attacks that exploit this kind of access
Run accessibility tests on a URL and return detailed violation reports. [${configNote}]. It is categorised as a Read tool in the Accessibility Testing MCP MCP Server, which means it retrieves data without modifying state.
Register the Accessibility Testing MCP server in PolicyLayer and add a rule for analyze_url: 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 Accessibility Testing MCP. Nothing to install.
analyze_url 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 analyze_url 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 analyze_url. 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.
analyze_url is provided by the Accessibility Testing MCP server (joe-watkins/accessibility-testing-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 →