find_clickable_elements

ServerScenic MCP
CategoryRead

How to control find_clickable_elements ↓

WHAT IT DOES

What find_clickable_elements does on Scenic MCP

AI agents call find_clickable_elements to retrieve information from Scenic MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why find_clickable_elements needs a policy

This tool performs semantic discovery and inspection of the viewport to identify available interactive elements. It has no side effects, does not modify application state, and does not execute commands. It is purely informational, making it a Read category tool with low severity since the worst an AI agent could do is waste tokens on unnecessary queries.

From the tool's definition Tool description states 'Find all clickable elements in the viewport' and 'discover what elements are available for interaction' — it retrieves and queries information about UI elements without modifying state or executing actions.

Documented attack patterns abuse exactly the kind of access find_clickable_elements gives an agent:

POLICY

How to control find_clickable_elements

PolicyLayer is an MCP gateway — it sits between your AI agents and Scenic MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for find_clickable_elements:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_clickable_elements": {}
  }
}

find_clickable_elements is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Scenic MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Scenic MCP tools

Execute click_element SEMANTIC CLICK: Click an element by its semantic ID. This is the high-level equivalent of Execute connect_scenic CONNECTION SETUP: Establish the connection to the ScenicMCP GenServer running inside our S Execute hover_element SEMANTIC HOVER: Move the mouse to hover over an element by its semantic ID. Finds the elem Execute send_keys KEYBOARD INPUT: Send text input or special keystrokes to the Scenic application. Use for t Execute send_mouse_click MOUSE INTERACTION: Click at specific screen coordinates to interact with buttons, links, a Execute send_mouse_move CURSOR MOVEMENT: Move the mouse cursor to specific coordinates. Useful for hover effects, Read get_scenic_status CONNECTION STATUS: Check if we are connected to a Scenic app and fetch details. Read inspect_viewport UI ANALYSIS: Get a detailed text-based description of what\

All 10 Scenic MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about find_clickable_elements

What does the find_clickable_elements tool do? +

SEMANTIC DISCOVERY: Find all clickable elements in the viewport with their semantic IDs, types, bounds, and center coordinates. Use this to discover what elements are available for interaction before clicking. Similar to Playwright\. It is categorised as a Read tool in the Scenic MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_clickable_elements? +

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

What risk level is find_clickable_elements? +

find_clickable_elements is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_clickable_elements? +

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

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

find_clickable_elements is provided by the Scenic MCP server (scenic-contrib/scenic_mcp_experimental). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Scenic MCP tool call.

Start from Scenic MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

10 Scenic MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.