user_mouse_input · Melo MCP: Risk & Policy

WHAT IT DOES

What user_mouse_input does on Melo

AI agents invoke user_mouse_input to trigger actions in Melo. 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 user_mouse_input needs a policy

This tool simulates user input (mouse clicks and movements) during an active Roblox playtest session. Simulating input drives real in-game actions whose effects depend entirely on what is clicked or where the mouse moves — triggering scripts, activating UI, manipulating game state.

From the tool's definition Simulate mouse clicks and movements during a playtest. Requires an active play session.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

user_mouse_input Rate-limited

user_mouse_input 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": {
    "user_mouse_input": {
      "limits": [
        {
          "counter": "user_mouse_input_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 Melo, so you can run agents against it safely.

FAQ

Questions about user_mouse_input

What does the user_mouse_input tool do? +

Simulate mouse clicks and movements during a playtest. Requires an active play session. Args: - action (string):. It is categorised as a Execute tool in the Melo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on user_mouse_input? +

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

What risk level is user_mouse_input? +

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

Can I rate-limit user_mouse_input? +

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

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

user_mouse_input is provided by the Melo MCP server (yannyhl/linkedsword-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

user_mouse_input is one line of Melo's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →