cc_keyboard_hotkey · K-Personal MCP: Risk & Policy

WHAT IT DOES

What cc_keyboard_hotkey does on K-Personal MCP

AI agents invoke cc_keyboard_hotkey to trigger actions in K-Personal 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 cc_keyboard_hotkey needs a policy

Keyboard hotkeys can trigger a wide range of system-level and application-level actions (e.g., Alt+F4 to close windows, Ctrl+Alt+Del, Win+R to run commands). This is an Execute-category action because it drives external operations whose effects depend on the specific key combination provided. The blast radius is high since hotkeys can control nearly any aspect of the OS or running applications.

From the tool's definition 단축키를 입력합니다 (Inputs a keyboard shortcut/hotkey) — triggers keyboard hotkey combinations that can invoke arbitrary system or application actions

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cc_keyboard_hotkey Rate-limited

cc_keyboard_hotkey 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": {
    "cc_keyboard_hotkey": {
      "limits": [
        {
          "counter": "cc_keyboard_hotkey_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 K-Personal MCP, so you can run agents against it safely.

FAQ

Questions about cc_keyboard_hotkey

What does the cc_keyboard_hotkey tool do? +

단축키를 입력합니다. 예: [. It is categorised as a Execute tool in the K-Personal 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 cc_keyboard_hotkey? +

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

What risk level is cc_keyboard_hotkey? +

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

Can I rate-limit cc_keyboard_hotkey? +

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

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

cc_keyboard_hotkey is provided by the K-Personal MCP server (lee30934-byte/k-personal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.