Run comprehensive accessibility scan using axe-core for WCAG compliance
AI agents invoke playwright_check_accessibility to trigger actions in RunAutomation 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.
This tool executes an automated accessibility scan against a browser session using the axe-core library. It triggers external operations (running a scan engine within a live browser context) rather than simply reading static data. The results depend on the current state of the browser session and the axe-core execution.
From the tool's definition Run comprehensive accessibility scan using axe-core for WCAG compliance
Documented attack patterns abuse exactly the kind of access playwright_check_accessibility gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RunAutomation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for playwright_check_accessibility:
{
"version": "1",
"default": "deny",
"tools": {
"playwright_check_accessibility": {
"limits": [
{
"counter": "playwright_check_accessibility_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} playwright_check_accessibility stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run comprehensive accessibility scan using axe-core for WCAG compliance. It is categorised as a Execute tool in the RunAutomation MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the RunAutomation MCP Server MCP server in PolicyLayer and add a rule for playwright_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 RunAutomation MCP Server. Nothing to install.
playwright_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 playwright_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 playwright_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.
playwright_check_accessibility is provided by the RunAutomation MCP Server MCP server (tayyabakmal1/runautomation-mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RunAutomation MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
91 RunAutomation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.