search_trademarks
Search the USPTO trademark database by name — a RANKED similarity/prefix search that returns the closest whole-mark matches (14M records). It is NOT an exhaustive contains-scan: multi-word marks that merely contain the queried word rank low and are usually cut (a KWIK query will miss KWIK REWARDS...
This record as markdown: /tools/com-gleanmark-trademark-search/search-trademarks.md
What search_trademarks does on GleanMark Trademark Search
AI agents call search_trademarks to retrieve information from GleanMark Trademark Search 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 |
|---|---|---|---|
limit | integer | — | Maximum number of results to return |
query | string | Yes | Search query for trademark name |
nice_classes | array | — | Filter by Nice Classification classes (1-45) |
status_filter | string | — | Filter by trademark status |
Parameters from the server's own tool schema.
Why search_trademarks is rated Low
This tool retrieves and queries data from a trademark database with no side effects. It returns search results based on similarity matching but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could perform excessive searches but cannot harm data or systems. This is a straightforward read operation.
From the tool's definition Tool performs 'RANKED similarity/prefix search' of trademark database, 'returns the closest whole-mark matches' from 14M records.
Attacks that exploit this kind of access
The rule that runs search_trademarks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GleanMark Trademark Search, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_trademarks, this is the rule to start with:
search_trademarks 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 GleanMark Trademark Search, apply this rule, and every search_trademarks call is checked against it from then on.
Questions about search_trademarks
Search the USPTO trademark database by name — a RANKED similarity/prefix search that returns the closest whole-mark matches (14M records). It is NOT an exhaustive contains-scan: multi-word marks that merely contain the queried word rank low and are usually cut (a KWIK query will miss KWIK REWARDS / KWIK KOPY). To enumerate ALL live marks containing a word — including compounds and respelled forms via USPTO pseudo-mark equivalents — use list_marks_containing_term instead. Thin results here are never proof a name is absent or available; availability questions belong to run_knockout_search. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
search_trademarks accepts 4 parameters: limit, query, nice_classes, status_filter. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the GleanMark Trademark Search MCP server in PolicyLayer and add a rule for search_trademarks: 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 GleanMark Trademark Search. Nothing to install.
search_trademarks 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_trademarks 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_trademarks. 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_trademarks is provided by the GleanMark Trademark Search MCP server (https://gleanmark.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GleanMark Trademark Search, and thousands of servers like it.
This server
Across the catalogue