tool_browser_press_key · Frappe MCP Server MCP

WHAT IT DOES

What tool_browser_press_key does on Frappe MCP Server

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

WHY IT NEEDS A POLICY

Why tool_browser_press_key needs a policy

Pressing keys in a browser can trigger form submissions, navigate pages, execute JavaScript shortcuts, or interact with UI elements in ways that have side effects. The empty description lowers confidence, but the pattern from sibling tools (browser_type, desktop_key) confirms this is an Execute-category tool. Misuse by an AI agent could trigger unintended actions in a browser session.

From the tool's definition Tool name 'tool_browser_press_key' suggests it simulates keyboard key presses in a browser context, similar to sibling tools like 'tool_desktop_key' and 'tool_browser_type' which perform browser/desktop interactions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tool_browser_press_key Rate-limited

tool_browser_press_key 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": {
    "tool_browser_press_key": {
      "limits": [
        {
          "counter": "tool_browser_press_key_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Frappe MCP Server, so you can run agents against it safely.

FAQ

Questions about tool_browser_press_key

What does the tool_browser_press_key tool do? +

tool_browser_press_key. It is categorised as a Execute tool in the Frappe MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tool_browser_press_key? +

Register the Frappe MCP Server MCP server in PolicyLayer and add a rule for tool_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 Frappe MCP Server. Nothing to install.

What risk level is tool_browser_press_key? +

tool_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 tool_browser_press_key? +

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

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

tool_browser_press_key is provided by the Frappe MCP Server MCP server (kallusuvaidyam/frappe_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.