tool_browser_close · Frappe MCP Server MCP: Risk & Policy

WHAT IT DOES

What tool_browser_close does on Frappe MCP Server

AI agents invoke tool_browser_close 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_close needs a policy

Based on the naming pattern and sibling tools, this tool likely closes a browser window or session — a browser action/execution operation. Empty description lowers confidence. Closing a browser is reversible but is an external operation execution, so Execute is the most appropriate category. Severity is medium as misuse could interrupt active browser sessions.

From the tool's definition Tool name: tool_browser_close; description is empty/uninformative. Sibling tools include tool_browser_screenshot, tool_browser_type, tool_browser_press_key, indicating a browser automation context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tool_browser_close Rate-limited

tool_browser_close 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_close": {
      "limits": [
        {
          "counter": "tool_browser_close_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_close

What does the tool_browser_close tool do? +

tool_browser_close. 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_close? +

Register the Frappe MCP Server MCP server in PolicyLayer and add a rule for tool_browser_close: 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_close? +

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

Can I rate-limit tool_browser_close? +

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

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

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