unclick_call
Call any UnClick tool endpoint. Specify the endpoint ID and parameters. Use unclick_search or unclick_tool_info to discover endpoint IDs and required params. Example: endpoint_id='image.resize', params={image: '<base64>', width: 800, height: 600}
This record as markdown: /tools/creativelead-unclick/unclick-call.md
What unclick_call does on UnClick
AI agents invoke unclick_call to trigger actions in UnClick. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
params | object | — | Parameters for the endpoint. Use unclick_tool_info to see required params. |
endpoint_id | string | — | Endpoint identifier, e.g. 'image.resize', 'hash.compute', 'csv.parse', 'cron.next' |
Parameters from the server's own tool schema.
Why unclick_call is rated High
This is a universal executor that can invoke any of 60+ tools across social, e-commerce, accounting, messaging, and financial platforms. The blast radius is critical because a single call could trigger financial transactions (Xero, Shopify), send messages (Slack, Discord), post public content (Reddit, Bluesky), or perform destructive operations—all depending on which endpoint is invoked.
From the tool's definition 'Call any UnClick tool endpoint' and 'endpoint_id' with arbitrary params spanning 'Slack, Reddit, Discord, Shopify, Xero, Bluesky' and '50+ more services'
Attacks that exploit this kind of access
The rule that runs unclick_call safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unclick_call, this is the rule to start with:
unclick_call 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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every unclick_call call is checked against it from then on.
Questions about unclick_call
Call any UnClick tool endpoint. Specify the endpoint ID and parameters. Use unclick_search or unclick_tool_info to discover endpoint IDs and required params. Example: endpoint_id='image.resize', params={image: '<base64>', width: 800, height: 600}. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
unclick_call accepts 2 parameters: params, endpoint_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for unclick_call: 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 UnClick. Nothing to install.
unclick_call 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 unclick_call 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 unclick_call. 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.
unclick_call is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue