os_move · OScribe MCP: Risk & Policy

WHAT IT DOES

What os_move does on OScribe

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

Moving the mouse cursor is a UI interaction/automation action that can trigger hover effects, tooltips, or precede clicks. It's part of desktop automation execution and has side effects in the UI context, though moving alone is less severe than clicking. Given this is part of a broader desktop automation suite, it warrants Execute classification with medium severity.

From the tool's definition Move mouse cursor to specific coordinates

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

os_move Rate-limited

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

FAQ

Questions about os_move

What does the os_move tool do? +

Move mouse cursor to specific coordinates. It is categorised as a Execute tool in the OScribe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on os_move? +

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

What risk level is os_move? +

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

Can I rate-limit os_move? +

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

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

os_move is provided by the OScribe MCP server (mikealkeal/oscribe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.