tool_desktop_key · Frappe MCP Server MCP: Risk & Policy

WHAT IT DOES

What tool_desktop_key does on Frappe MCP Server

AI agents invoke tool_desktop_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_desktop_key needs a policy

Based on the tool name pattern and sibling tools like 'tool_browser_press_key' and 'tool_browser_type', this tool likely simulates keyboard input on the desktop environment. Keyboard input can trigger arbitrary actions including executing commands, confirming destructive dialogs, or navigating UI. The empty description lowers confidence, but the Execute category is most appropriate given the likely functionality.

From the tool's definition Tool name 'tool_desktop_key' suggests keyboard input simulation on the desktop; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tool_desktop_key Rate-limited

tool_desktop_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_desktop_key": {
      "limits": [
        {
          "counter": "tool_desktop_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_desktop_key

What does the tool_desktop_key tool do? +

tool_desktop_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_desktop_key? +

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

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

Can I rate-limit tool_desktop_key? +

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

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

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