cc_keyboard_type · K-Personal MCP: Risk & Policy

WHAT IT DOES

What cc_keyboard_type does on K-Personal MCP

AI agents invoke cc_keyboard_type 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_type needs a policy

Typing arbitrary text into the active window is an Execute-level action: it triggers external operations (keystrokes delivered to whatever application has focus) whose effects depend entirely on the arguments and context. Misuse could submit forms, issue commands in terminals, alter documents, or interact with any UI element — making the blast radius high.

From the tool's definition 키보드로 입력합니다 — types keyboard input including Korean text into the currently focused application

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cc_keyboard_type Rate-limited

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

FAQ

Questions about cc_keyboard_type

What does the cc_keyboard_type 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_type? +

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

What risk level is cc_keyboard_type? +

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

Can I rate-limit cc_keyboard_type? +

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

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

cc_keyboard_type 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.