element_click

Click an element. Toggles checkbox if element type is checkbox.

SERVERMcp Anything SOURCEZaymadkid/mcp-anything

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/mcp-anything/element-click.md

WHAT IT DOES

What element_click does on Mcp Anything

AI agents invoke element_click to trigger actions in Mcp Anything. 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 element_click is rated High

Clicking UI elements triggers actions whose effects depend entirely on what element is clicked — could submit forms, trigger operations, toggle state, etc. This is a browser/UI action that executes an interaction, making it Execute category. Effects are variable and context-dependent, warranting medium severity.

From the tool's definition Click an element. Toggles checkbox if element type is checkbox.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs element_click safely

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

element_click Rate-limited

element_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": {
    "element_click": {
      "limits": [
        {
          "counter": "element_click_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 Mcp Anything, apply this rule, and every element_click call is checked against it from then on.

FAQ

Questions about element_click

What does the element_click tool do? +

Click an element. Toggles checkbox if element type is checkbox. It is categorised as a Execute tool in the Mcp Anything MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on element_click? +

Register the Mcp Anything MCP server in PolicyLayer and add a rule for element_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 Mcp Anything. Nothing to install.

What risk level is element_click? +

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

Can I rate-limit element_click? +

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

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

element_click is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Anything, and thousands of servers like it.

This server

All 261 Mcp Anything 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 →