find_element

Find web element using various strategies

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/find-element.md

WHAT IT DOES

What find_element does on Ncp

AI agents invoke find_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 find_element is rated High

Finding web elements requires driving a browser or web automation context, which is an active external operation (Execute category). While a pure element lookup may seem read-like, it operates within a live browser session and is a prerequisite step in browser automation chains. Misuse could facilitate scraping or UI manipulation.

From the tool's definition "Find web element using various strategies" — interacts with a live browser/web session to locate DOM elements, which constitutes an external browser action

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_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 find_element, this is the rule to start with:

find_element Rate-limited

find_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": {
    "find_element": {
      "limits": [
        {
          "counter": "find_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 find_element call is checked against it from then on.

FAQ

Questions about find_element

What does the find_element tool do? +

Find web element using various strategies. 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 find_element? +

Register the Ncp MCP server in PolicyLayer and add a rule for find_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 find_element? +

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

Can I rate-limit find_element? +

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

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

find_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_wait_for_element on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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