Run accessibility tests on the current page
AI agents invoke check_accessibility to trigger actions in AutoSpectra MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes an automated accessibility audit/scan against the current browser page. It triggers external operations (browser inspection, rule evaluation) rather than merely reading static data. It has no financial or destructive implications, but it does execute a test run on a live environment, making Execute the appropriate category.
From the tool's definition 'Run accessibility tests on the current page' — actively runs tests (executes operations) against a live browser page
Attacks that exploit this kind of access
Run accessibility tests on the current page. It is categorised as a Execute tool in the AutoSpectra MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AutoSpectra MCP Server MCP server in PolicyLayer and add a rule for check_accessibility: 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 AutoSpectra MCP Server. Nothing to install.
check_accessibility is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the check_accessibility 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 check_accessibility. 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.
check_accessibility is provided by the AutoSpectra MCP Server MCP server (raphaenterprises-ai/autospectra-mcp-server). 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 →