web_click · K-Personal MCP: Risk & Policy

WHAT IT DOES

What web_click does on K-Personal MCP

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

Clicking web elements can trigger arbitrary actions in a browser context (form submissions, purchases, navigation, deletions), making this an Execute-level tool with high severity due to unpredictable side effects depending on what element is clicked.

From the tool's definition web_click — clicks elements in a headless browser via selector or role+name; triggers external operations whose effects depend on arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

web_click Rate-limited

web_click 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": {
    "web_click": {
      "limits": [
        {
          "counter": "web_click_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 web_click

What does the web_click tool do? +

selector 또는 role+name 으로 요소 클릭. 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 web_click? +

Register the K-Personal MCP server in PolicyLayer and add a rule for web_click: 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 web_click? +

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

Can I rate-limit web_click? +

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

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

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