unclick_tool_info
Get detailed information about a specific UnClick tool including all its endpoints, required parameters, and response shapes. Use this after unclick_search to understand exactly how to call a tool.
This record as markdown: /tools/creativelead-unclick/unclick-tool-info.md
What unclick_tool_info does on UnClick
AI agents call unclick_tool_info to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | — | Tool slug, e.g. 'image', 'hash', 'csv', 'cron'. Available slugs: transform, encode, hash, regex, markdown, diff, json, csv, validate, image, qr, color, timestam |
Parameters from the server's own tool schema.
Why unclick_tool_info is rated Low
This tool retrieves metadata about other UnClick tools (endpoints, parameters, response shapes). It is a lookup/query operation with no ability to execute, modify, delete, or trigger financial transactions. The low severity reflects that misuse yields only informational exposure, not operational harm.
From the tool's definition Tool description states it 'Get[s] detailed information' and 'understand[s] how to call a tool' — purely informational retrieval with no side effects, data modification, or external action triggering.
Attacks that exploit this kind of access
The rule that runs unclick_tool_info 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_tool_info, this is the rule to start with:
unclick_tool_info is read-only, so it stays allowed. 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_tool_info call is checked against it from then on.
Questions about unclick_tool_info
Get detailed information about a specific UnClick tool including all its endpoints, required parameters, and response shapes. Use this after unclick_search to understand exactly how to call a tool. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
unclick_tool_info accepts 1 parameter: slug. 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_tool_info: 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_tool_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the unclick_tool_info 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_tool_info. 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_tool_info 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.
This server
Across the catalogue