search_design_codes

SERVERGleanMark Trademark Search SOURCEhttps://gleanmark.com/mcp

Low RISK CLASS

Category Read

Parameters 90 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-gleanmark-trademark-search/search-design-codes.md

WHAT IT DOES

What search_design_codes does on GleanMark Trademark Search

AI agents call search_design_codes 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
`mode`	string	—	search_codes = find a code from a word. describe_code = what a code means. count/top_owners/list_marks = marks carrying the codes. Omit it and the mode is infer
`codes`	array	—	Design codes, dotted or packed, e.g. ["26.17.01"].
`limit`	integer	—
`match`	string	—	all = mark carries every code. any = at least one.
`query`	string	—	Required for mode="search_codes". A shape word: band, bar, circle, star, triangle, chevron, crown, leaf, arrow, shield.
`status`	string	—
`nice_class`	string	—	Restrict to one Nice class, e.g. "25".
`serial_number`	string	—	Eight-digit serial number for mode="by_serial".
`registration_number`	string	—	Registration number for mode="by_serial"; resolved to its serial number automatically.

Parameters from the server's own tool schema.

RISK

Why search_design_codes is rated Low

Even though search_design_codes only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_design_codes 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_design_codes, this is the rule to start with:

search_design_codes Allowed

search_design_codes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_design_codes": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GleanMark Trademark Search, apply this rule, and every search_design_codes call is checked against it from then on.

FAQ

Questions about search_design_codes

What does the search_design_codes tool do? +

Find US trademarks by USPTO design code — the codes examiners assign to the visual elements of a logo (26.17.01 = straight bands, 24.11 = crowns). Accepts dotted (26.17.01) or packed (261701) form. USPTO design vocabulary is literal and narrow: it records "Bands, straight" where a person says "stripe", and has no entry for words like "swoosh", so a plain shape word resolves to a code through mode="search_codes" before marks can be counted or listed. Modes: count, top_owners, list_marks, by_serial (what codes one mark carries), describe_code, search_codes. Omitting mode infers it from the arguments supplied. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.

What parameters does search_design_codes accept? +

search_design_codes accepts 9 parameters: mode, codes, limit, match, query, status, nice_class, serial_number, registration_number. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on search_design_codes? +

Register the GleanMark Trademark Search MCP server in PolicyLayer and add a rule for search_design_codes: 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.

What risk level is search_design_codes? +

search_design_codes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_design_codes? +

Yes. Add a rate_limit block to the search_design_codes 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.

How do I block search_design_codes completely? +

Set action: deny in the PolicyLayer policy for search_design_codes. 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.

What MCP server provides search_design_codes? +

search_design_codes 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.

KEEP EXPLORING

More on GleanMark Trademark Search, and thousands of servers like it.

This server

All 61 GleanMark Trademark Search tools →

Across the catalogue

evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →