New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

search_claimed_colors

Search or count US trademarks by the colours they claim, parsed from USPTO colour-claim statements. Neither TESS nor its successor offers this. TWO levels: level="family" (16 families; searching "red" also finds dark red, maroon, burgundy) and level="shade" (the exact term as claimed, e.g. "dark ...

SERVERGleanMark Trademark Search SOURCEhttps://gleanmark.com/mcp
Low RISK CLASS
Category Read
Parameters 110 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-claimed-colors.md

What search_claimed_colors does on GleanMark Trademark Search

AI agents call search_claimed_colors 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.

ParameterTypeRequiredDescription
mode string count = how many marks match. top_owners = who owns the most. list_marks = sample the matches. vocabulary = valid colour terms + corpus counts. explain_term = a
term string Required for mode="explain_term", e.g. "maroon".
level string family = 16 broad families (red covers maroon). shade = the exact claimed term.
limit integer Rows for top_owners, list_marks, vocabulary.
match string all = claims at least these. only = claims exactly these, nothing else. only_bw = exactly these, allowing black/white (usually background).
colors array Colour terms, e.g. ["orange","green","red"]. Must be real families or shades — call mode="vocabulary" if unsure. Omit to match every colour-claiming mark.
status string registered/pending are narrower than live. "How many live REGISTRATIONS" means status="registered".
claimed boolean false = count marks whose statement disclaims colour ("Color is not claimed as a feature of the mark").
nice_class string Restrict to one Nice class, e.g. "25" or "025".
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.

Why search_claimed_colors is rated Low

This tool queries and retrieves trademark information from the USPTO database using various filters (color families, shades, match types). All operations are read-only: search, count, list, and vocabulary modes retrieve data but do not create, modify, delete, or execute arbitrary operations. The low severity reflects minimal blast radius—misuse would return unwanted search results but cannot harm systems or data.

From the tool's definition Tool performs search and count operations on trademark data: 'Search or count US trademarks', 'count marks', 'list_marks', 'top_owners'. Returns data without modification or side effects. No mutations to the database or external systems.

Risk signalsHigh parameter count (11 properties)

Questions about search_claimed_colors

What does the search_claimed_colors tool do? +

Search or count US trademarks by the colours they claim, parsed from USPTO colour-claim statements. Neither TESS nor its successor offers this. TWO levels: level="family" (16 families; searching "red" also finds dark red, maroon, burgundy) and level="shade" (the exact term as claimed, e.g. "dark red"). Use match="all" for "claims at least these colours", match="only" for "claims exactly these and nothing else", match="only_bw" to also tolerate black/white. Set claimed=false to count marks whose statement DISCLAIMS colour. Modes: count, top_owners, list_marks, vocabulary (list the valid families or shades with corpus counts), explain_term (which family a shade belongs to), by_serial (what one mark claims). 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_claimed_colors accept? +

search_claimed_colors accepts 11 parameters: mode, term, level, limit, match, colors, status, claimed, 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_claimed_colors? +

Register the GleanMark Trademark Search MCP server in PolicyLayer and add a rule for search_claimed_colors: 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_claimed_colors? +

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

Can I rate-limit search_claimed_colors? +

Yes. Add a rate_limit block to the search_claimed_colors 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_claimed_colors completely? +

Set action: deny in the PolicyLayer policy for search_claimed_colors. 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_claimed_colors? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GleanMark Trademark Search's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.