Click an element on the page specified by its numbered label from the annotated screenshot
AI agents invoke click to trigger actions in Steel 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.
Clicking is a browser action that executes external operations with effects entirely dependent on what element is clicked. It can trigger purchases, form submissions, account changes, deletions, or any other web action, making it Execute-category with high severity due to the broad blast radius of an AI agent clicking arbitrary web elements.
From the tool's definition 'Click an element on the page specified by its numbered label from the annotated screenshot' — triggers browser click actions that can submit forms, activate buttons, navigate pages, or initiate any web interaction
Documented attack patterns abuse exactly the kind of access click gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Steel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for click:
{
"version": "1",
"default": "deny",
"tools": {
"click": {
"limits": [
{
"counter": "click_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Click an element on the page specified by its numbered label from the annotated screenshot. It is categorised as a Execute tool in the Steel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Steel MCP Server MCP server in PolicyLayer and add a rule for 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 Steel MCP Server. Nothing to install.
click is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
click is provided by the Steel MCP Server MCP server (steel-dev/steel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Steel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Steel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.