compare_marks
Compare two trademarks for likelihood of confusion using DuPont-style analysis. Returns similarity scores and risk assessment.
This record as markdown: /tools/com-gleanmark-trademark-search/compare-marks.md
What compare_marks does on GleanMark Trademark Search
AI agents call compare_marks 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 |
|---|---|---|---|
mark_a | string | Yes | First trademark to compare |
mark_b | string | Yes | Second trademark to compare |
nice_classes | array | — | Nice classes for overlap analysis |
Parameters from the server's own tool schema.
Why compare_marks is rated Low
This tool queries trademark data and performs analytical comparison, characteristic of Read operations. No data is created, modified, deleted, or executed. The output is informational (scores and assessment) intended to inform legal decision-making but does not itself modify USPTO records, commit financial obligations, or trigger irreversible actions.
From the tool's definition compare_marks performs analysis and returns similarity scores and risk assessment—pure data retrieval with no creation, modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs compare_marks 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 compare_marks, this is the rule to start with:
compare_marks 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 compare_marks call is checked against it from then on.
Questions about compare_marks
Compare two trademarks for likelihood of confusion using DuPont-style analysis. Returns similarity scores and risk assessment. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
compare_marks accepts 3 parameters: mark_a, mark_b, nice_classes. Required: mark_a, mark_b. 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 compare_marks: 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.
compare_marks 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 compare_marks 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 compare_marks. 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.
compare_marks 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