Click on an element
AI agents invoke click to trigger actions in AutoSpectra 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.
Browser click actions are Execute-category because their side effects are entirely argument-dependent. A misused click could trigger destructive or financial operations (e.g., clicking a 'delete' button or 'confirm payment'), making this high severity in an AI agent context.
From the tool's definition Tool name 'click' and description 'Click on an element' — triggers browser automation action whose effects depend on what element is clicked (could submit forms, confirm purchases, delete records, navigate pages, etc.)
Attacks that exploit this kind of access
Click on an element. It is categorised as a Execute tool in the AutoSpectra MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AutoSpectra 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 AutoSpectra 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 AutoSpectra MCP Server MCP server (raphaenterprises-ai/autospectra-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →