New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

browser_press_key

Press a key on the keyboard

SERVERA11y Agent Skills SOURCEsmukh/a11y-agent-skills
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a11y-agent-skills/browser-press-key.md

What browser_press_key does on A11y Agent Skills

AI agents invoke browser_press_key to trigger actions in A11y Agent Skills. 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.

Why browser_press_key is rated High

Pressing a key triggers browser interactions that can have side effects depending on what is focused — submitting forms, navigating pages, deleting text, or triggering shortcuts. The effect depends entirely on the browser state at the time, making this an Execute-category action. Severity is medium because misuse can trigger unintended actions but is generally bounded by the current browser context.

From the tool's definition Press a key on the keyboard

Questions about browser_press_key

What does the browser_press_key tool do? +

Press a key on the keyboard. It is categorised as a Execute tool in the A11y Agent Skills MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_press_key? +

Register the A11y Agent Skills MCP server in PolicyLayer and add a rule for browser_press_key: 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 A11y Agent Skills. Nothing to install.

What risk level is browser_press_key? +

browser_press_key is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_press_key? +

Yes. Add a rate_limit block to the browser_press_key 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.

How do I block browser_press_key completely? +

Set action: deny in the PolicyLayer policy for browser_press_key. 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 browser_press_key? +

browser_press_key is provided by the A11y Agent Skills MCP server (smukh/a11y-agent-skills). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on A11y Agent Skills, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of A11y Agent Skills's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.