This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/search-patents.md
What search_patents does on UnClick
AI agents call search_patents 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 |
|---|---|---|---|
query | string | Yes | |
status | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why search_patents is rated Low
Searching a public patent database is a non-destructive information retrieval operation. It does not create, modify, delete, or execute any operations. The action is purely exploratory and returns existing public data. This is a classic Read operation with minimal security risk.
From the tool's definition Tool name is 'search_patents' and description states 'Search Australian patents via IP Australia' — the verb 'search' and the read-only nature of querying a public patent database indicate data retrieval with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs search_patents 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 search_patents, this is the rule to start with:
search_patents 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 search_patents call is checked against it from then on.
Questions about search_patents
Search Australian patents via IP Australia. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
search_patents accepts 3 parameters: query, status, api_key. Required: query. 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 search_patents: 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.
search_patents 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 search_patents 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 search_patents. 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.
search_patents is provided by the UnClick MCP server (@unclick/mcp-server). 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