unclick_browse
Browse all available UnClick tools, optionally filtered by category. Returns a list of tools with their slugs and descriptions.
This record as markdown: /tools/creativelead-unclick/unclick-browse.md
What unclick_browse does on UnClick
AI agents call unclick_browse 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 |
|---|---|---|---|
category | string | — | Optional: filter to a specific category |
Parameters from the server's own tool schema.
Why unclick_browse is rated Low
This tool queries and retrieves metadata about available tools in the UnClick marketplace. It performs a read-only operation that retrieves information without modifying, executing, or deleting any data. The action has minimal blast radius—an AI agent using it can only discover what tools are available, which is informational in nature.
From the tool's definition Tool description states it 'Browse all available UnClick tools' and 'Returns a list of tools with their slugs and descriptions.' The verb 'browse' and 'returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs unclick_browse 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_browse, this is the rule to start with:
unclick_browse 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_browse call is checked against it from then on.
Questions about unclick_browse
Browse all available UnClick tools, optionally filtered by category. Returns a list of tools with their slugs and descriptions. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
unclick_browse accepts 1 parameter: category. 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_browse: 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_browse 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_browse 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_browse. 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_browse 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