Scan multiple URLs for accessibility violations
AI agents call scan_urls to retrieve information from aria51 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves accessibility data and reports violations but does not create, modify, delete, or execute operations on the scanned systems. It is a passive inspection/detection tool with no side effects beyond generating audit reports. Severity is low because misuse would at worst result in excessive scanning requests, not data loss or code execution.
From the tool's definition Tool performs scanning and detection of accessibility violations without modifying, deleting, or executing code on target systems. Description states 'Scan multiple URLs for accessibility violations' — purely analytical.
Attacks that exploit this kind of access
Scan multiple URLs for accessibility violations. It is categorised as a Read tool in the aria51 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the aria51 MCP Server MCP server in PolicyLayer and add a rule for scan_urls: 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 aria51 MCP Server. Nothing to install.
scan_urls 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 scan_urls 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 scan_urls. 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.
scan_urls is provided by the aria51 MCP Server MCP server (justinleeirizarry/aria51). 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 →