tool_desktop_open_app · Frappe MCP Server MCP: Risk & Policy

WHAT IT DOES

What tool_desktop_open_app does on Frappe MCP Server

AI agents invoke tool_desktop_open_app 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_desktop_open_app needs a policy

Opening a desktop application is an Execute-category action as it triggers an external operation. However, the empty description significantly lowers confidence. Given the server context (Frappe bench/site management, browser and desktop interaction tools), this likely opens a GUI application on the desktop, which constitutes executing an external process.

From the tool's definition Tool name 'tool_desktop_open_app' implies launching a desktop application; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tool_desktop_open_app Rate-limited

tool_desktop_open_app 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_desktop_open_app": {
      "limits": [
        {
          "counter": "tool_desktop_open_app_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_desktop_open_app

What does the tool_desktop_open_app tool do? +

tool_desktop_open_app. 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_desktop_open_app? +

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

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

Can I rate-limit tool_desktop_open_app? +

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

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

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