search_mark_statements
Search the statements USPTO records on a trademark: disclaimer ("no claim is made to PIZZA apart from the mark"), description (the examiner's written description of the drawing — "the mark consists of a red and white striped awning"), translation (foreign wording), prior_marks (claimed ownership ...
This record as markdown: /tools/com-gleanmark-trademark-search/search-mark-statements.md
What search_mark_statements does on GleanMark Trademark Search
AI agents call search_mark_statements 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 | — | |
text | string | — | Free text to find inside the statement, minimum 3 characters (e.g. "PIZZA", "stripe"). Omit to count every mark carrying that statement type. |
limit | integer | — | |
status | string | — | |
nice_class | string | — | Restrict to one Nice class, e.g. "25". |
serial_number | string | — | Eight-digit serial number for mode="by_serial". |
statement_type | string | — | Required except for by_serial and statement_types. |
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_mark_statements is rated Low
This tool retrieves and queries historical trademark statement data from USPTO records without any side effects. It performs passive searches and analysis of existing trademark information (disclaimers, descriptions, translations, prior marks). The blast radius of misuse is minimal—an agent cannot harm data or systems through search operations, only access information that is already public USPTO record data.
From the tool's definition Tool description explicitly states it 'search[es]' USPTO records and 'answers' queries about trademark statements. The modes listed (count, top_owners, list_marks, by_serial, statement_type) are all retrieval and analytical operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs search_mark_statements 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_mark_statements, this is the rule to start with:
search_mark_statements 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_mark_statements call is checked against it from then on.
Questions about search_mark_statements
Search the statements USPTO records on a trademark: disclaimer ("no claim is made to PIZZA apart from the mark"), description (the examiner's written description of the drawing — "the mark consists of a red and white striped awning"), translation (foreign wording), prior_marks (claimed ownership of earlier registrations). Answers "which marks disclaim PIZZA" and "which marks are described as stripes". Colour claims have their own tool (search_claimed_colors); goods text is served by search_trademarks. Modes: count, top_owners, list_marks, by_serial (every statement on one mark), statement_types. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
search_mark_statements accepts 8 parameters: mode, text, limit, status, nice_class, serial_number, statement_type, registration_number. 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_mark_statements: 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_mark_statements 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_mark_statements 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_mark_statements. 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_mark_statements 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