현재 마우스 커서의 좌표를 반환합니다.
AI agents call cc_mouse_position to retrieve information from K-Personal MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns the current mouse cursor position. It has no side effects, does not modify any state, and cannot cause harm on its own.
From the tool's definition 현재 마우스 커서의 좌표를 반환합니다 — 'returns the current mouse cursor coordinates'
Attacks that exploit this kind of access
현재 마우스 커서의 좌표를 반환합니다. It is categorised as a Read tool in the K-Personal MCP MCP Server, which means it retrieves data without modifying state.
Register the K-Personal MCP server in PolicyLayer and add a rule for cc_mouse_position: 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.
cc_mouse_position is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cc_mouse_position 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.
Set action: deny in the PolicyLayer policy for cc_mouse_position. 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.
cc_mouse_position 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →