Run accessibility audit
AI agents invoke ira_audit_accessibility to trigger actions in IRA-RESEARCHER. 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.
This tool executes an operation (accessibility audit) whose effects depend on the browser context and target page. While not destructive or writing data, it runs code-like functionality to analyze and report on page properties. It's Execute rather than Read because it actively runs an audit process (execution) rather than passively retrieving existing data.
From the tool's definition Tool performs 'Run accessibility audit' which executes an automated audit operation on a webpage or browser context, triggering external analysis tools and generating analysis results as a side effect.
Attacks that exploit this kind of access
Run accessibility audit. It is categorised as a Execute tool in the IRA-RESEARCHER MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the IRA-RESEARCHER MCP server in PolicyLayer and add a rule for ira_audit_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 IRA-RESEARCHER. Nothing to install.
ira_audit_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 ira_audit_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 ira_audit_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.
ira_audit_accessibility is provided by the IRA-RESEARCHER MCP server (neuralnexustech/ira-researcher). 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 →