input_device_control

Read or explicitly enable/disable the locally detected touchpad or touchscreen using Omarchy

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/omarchy-mcp/input-device-control.md

WHAT IT DOES

What input_device_control does on Omarchy-MCP

AI agents invoke input_device_control to trigger actions in Omarchy-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.

RISK

Why input_device_control is rated High

Toggling input devices affects system usability and can lock out user interaction.

From the tool's definition explicitly enable/disable the locally detected touchpad or touchscreen

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs input_device_control safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Omarchy-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For input_device_control, this is the rule to start with:

input_device_control Rate-limited

input_device_control 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": {
    "input_device_control": {
      "limits": [
        {
          "counter": "input_device_control_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every input_device_control call is checked against it from then on.

FAQ

Questions about input_device_control

What does the input_device_control tool do? +

Read or explicitly enable/disable the locally detected touchpad or touchscreen using Omarchy. It is categorised as a Execute tool in the Omarchy-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 input_device_control? +

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

What risk level is input_device_control? +

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

Can I rate-limit input_device_control? +

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

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

input_device_control is provided by the Omarchy MCP server (hlsitechio/Omarchy-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Omarchy, and thousands of servers like it.

This server

All 466 Omarchy tools → High-risk tools on this server →

Across the catalogue

adb_backup_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →