desktop_type · Universal Dev MCP: Risk & Policy

WHAT IT DOES

What desktop_type does on Universal Dev MCP

AI agents invoke desktop_type to trigger actions in Universal Dev MCP. 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 desktop_type needs a policy

This tool simulates keyboard input into a focused window, which is an external operation akin to browser/desktop automation. It can trigger form submissions, commands, or other side effects depending on what receives the input. Severity is medium because misuse could cause unintended input into sensitive fields, but it requires a focused window context.

From the tool's definition 'Focused window mein text type karo' — types text into a focused window, a browser/desktop interaction action

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

desktop_type Rate-limited

desktop_type 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": {
    "desktop_type": {
      "limits": [
        {
          "counter": "desktop_type_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 Universal Dev MCP, so you can run agents against it safely.

FAQ

Questions about desktop_type

What does the desktop_type tool do? +

Focused window mein text type karo (Unicode support). It is categorised as a Execute tool in the Universal Dev MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on desktop_type? +

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

What risk level is desktop_type? +

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

Can I rate-limit desktop_type? +

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

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

desktop_type is provided by the Universal Dev MCP server (kallusuvaidyam/universal_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.