test_accessibility_audit
A read tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/test-accessibility-audit.md
What test_accessibility_audit does on Looking Glass
AI agents call test_accessibility_audit to retrieve information from Looking Glass without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why test_accessibility_audit is rated Low
The name suggests an accessibility audit, which is typically a read/analysis operation that inspects a page for accessibility issues without modifying anything. However, the empty description lowers confidence significantly. Based on naming conventions and the context of a browser automation tool, this is most likely a passive read/audit operation.
From the tool's definition Tool name: test_accessibility_audit — description is empty/uninformative
Attacks that exploit this kind of access
The rule that runs test_accessibility_audit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test_accessibility_audit, this is the rule to start with:
test_accessibility_audit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every test_accessibility_audit call is checked against it from then on.
Questions about test_accessibility_audit
test_accessibility_audit is a read tool on the Looking Glass MCP server. It is categorised as a Read tool in the Looking Glass MCP Server, which means it retrieves data without modifying state.
Register the Looking Glass MCP server in PolicyLayer and add a rule for test_accessibility_audit: 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 Looking Glass. Nothing to install.
test_accessibility_audit 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_accessibility_audit 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_accessibility_audit. 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_accessibility_audit is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Looking Glass, and thousands of servers like it.
This server
Across the catalogue