click-element · TgeBrowser MCP Server MCP: Risk & Policy

WHAT IT DOES

What click-element does on TgeBrowser MCP Server

AI agents invoke click-element to trigger actions in TgeBrowser MCP Server. 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 click-element needs a policy

Clicking an element performs a browser action whose effects depend entirely on what is being clicked (submitting forms, navigating pages, triggering purchases, etc.). This is an Execute-category action as it runs a browser automation operation with context-dependent side effects.

From the tool's definition 'Click the element' — triggers a browser interaction/action on a DOM element

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

click-element Rate-limited

click-element 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": {
    "click-element": {
      "limits": [
        {
          "counter": "click-element_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 TgeBrowser MCP Server, so you can run agents against it safely.

FAQ

Questions about click-element

What does the click-element tool do? +

Click the element. It is categorised as a Execute tool in the TgeBrowser MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on click-element? +

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

What risk level is click-element? +

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

Can I rate-limit click-element? +

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

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

click-element is provided by the TgeBrowser MCP Server MCP server (tuguang2025/tgebrowser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.