click_element

Click on a web element

SERVERNcp SOURCE@portel/ncp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-portel-dev-ncp/click-element.md

WHAT IT DOES

What click_element does on Ncp

AI agents invoke click_element to trigger actions in Ncp. 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.

RISK

Why click_element is rated High

Clicking a web element is a browser automation action (Execute category). The actual impact varies widely based on context — clicking a submit button on a payment form could be Financial, clicking a delete button could be Destructive — but since the tool itself is a general-purpose click action, Execute is the most accurate base category.

From the tool's definition 'Click on a web element' — triggers a browser action that interacts with external web interfaces, whose effects depend entirely on which element is clicked (could submit forms, trigger purchases, delete data, etc.)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs click_element safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For click_element, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every click_element call is checked against it from then on.

FAQ

Questions about click_element

What does the click_element tool do? +

Click on a web element. It is categorised as a Execute tool in the Ncp 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 Ncp 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 Ncp. 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 Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server →qt_click on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →