run_dupont_analysis
Run a full 13-factor DuPont likelihood of confusion analysis between two trademarks. Includes web research on the companies, market overlap analysis, and detailed factor-by-factor scoring. This is the most thorough confusion analysis available — use compare_marks for a quick check first.
This record as markdown: /tools/com-gleanmark-trademark-search/run-dupont-analysis.md
What run_dupont_analysis does on GleanMark Trademark Search
AI agents call run_dupont_analysis 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 |
|---|---|---|---|
serial_a | string | Yes | USPTO serial number of the first mark |
serial_b | string | Yes | USPTO serial number of the second mark |
Parameters from the server's own tool schema.
Why run_dupont_analysis is rated Low
The tool performs analysis and retrieval of information — it queries trademark data, conducts web research, and scores factors. There are no write, execute, destructive, or financial side effects described. The medium severity reflects the sensitivity of legal/IP analysis that could influence business decisions if misused or misinterpreted.
From the tool's definition 'Run a full 13-factor DuPont likelihood of confusion analysis between two trademarks. Includes web research on the companies, market overlap analysis, and detailed factor-by-factor scoring.'
Attacks that exploit this kind of access
The rule that runs run_dupont_analysis 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 run_dupont_analysis, this is the rule to start with:
run_dupont_analysis 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 run_dupont_analysis call is checked against it from then on.
Questions about run_dupont_analysis
Run a full 13-factor DuPont likelihood of confusion analysis between two trademarks. Includes web research on the companies, market overlap analysis, and detailed factor-by-factor scoring. This is the most thorough confusion analysis available — use compare_marks for a quick check first. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
run_dupont_analysis accepts 2 parameters: serial_a, serial_b. Required: serial_a, serial_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 run_dupont_analysis: 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.
run_dupont_analysis 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 run_dupont_analysis 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 run_dupont_analysis. 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.
run_dupont_analysis 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