Medium Risk

audit_keyboard

Audit keyboard tab order, focus visibility, jumps, skip links, and focus traps.

High parameter count (14 properties)

Part of the Mcp Accessibility Scanner MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

mcp-accessibility-scanner Write Risk 2/5

AI agents use audit_keyboard to create or modify resources in Mcp Accessibility Scanner. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call audit_keyboard repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Accessibility Scanner.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-justasmonkev-mcp-accessibility-scanner.yaml
tools:
  audit_keyboard:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Mcp Accessibility Scanner policy for all 27 tools.

Tool Name audit_keyboard
Category Write
Risk Level Medium

View all 27 tools →

Agents calling write-class tools like audit_keyboard have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the audit_keyboard tool do? +

Audit keyboard tab order, focus visibility, jumps, skip links, and focus traps.. It is categorised as a Write tool in the Mcp Accessibility Scanner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on audit_keyboard? +

Add a rule in your Intercept YAML policy under the tools section for audit_keyboard. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Accessibility Scanner MCP server.

What risk level is audit_keyboard? +

audit_keyboard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit audit_keyboard? +

Yes. Add a rate_limit block to the audit_keyboard rule in your Intercept 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.

How do I block audit_keyboard completely? +

Set action: deny in the Intercept policy for audit_keyboard. 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.

What MCP server provides audit_keyboard? +

audit_keyboard is provided by the Mcp Accessibility Scanner MCP server (mcp-accessibility-scanner). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mcp Accessibility Scanner

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.