browser_press

Press a keyboard key (e.g. Enter, Tab).

SERVERLocalAnt SOURCEyuga-hashimoto/localant

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/yuga-hashimoto-localant/browser-press.md

WHAT IT DOES

What browser_press does on LocalAnt

AI agents invoke browser_press to trigger actions in LocalAnt. 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.

RISK

Why browser_press is rated High

This tool triggers browser keyboard input actions, which are external operations that can have variable effects depending on context — submitting forms, navigating pages, confirming dialogs, etc. It's an action/execution tool rather than a simple read or write, as it drives browser behavior in ways that depend on the current state and arguments.

From the tool's definition Press a keyboard key (e.g. Enter, Tab)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_press safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_press, this is the rule to start with:

browser_press Rate-limited

browser_press 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_press": {
      "limits": [
        {
          "counter": "browser_press_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every browser_press call is checked against it from then on.

FAQ

Questions about browser_press

What does the browser_press tool do? +

Press a keyboard key (e.g. Enter, Tab). It is categorised as a Execute tool in the LocalAnt 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? +

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

What risk level is browser_press? +

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

Can I rate-limit browser_press? +

Yes. Add a rate_limit block to the browser_press 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 completely? +

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

browser_press is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server →qt_key_press on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →