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

resolve_trademark_subject

Resolve an owner, law firm, correspondent, mark, TTAB proceeding, client, or portfolio to the best trademark entity match. Resolving clients and portfolios requires authentication.

SERVERGleanMark Trademark Search SOURCEhttps://gleanmark.com/mcp
Low RISK CLASS
Category Read
Parameters 32 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-gleanmark-trademark-search/resolve-trademark-subject.md

What resolve_trademark_subject does on GleanMark Trademark Search

AI agents call resolve_trademark_subject 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
limit integer Maximum number of candidate matches to return.
entity string Yes What kind of trademark subject to resolve.
subject_name string Yes Raw owner, firm, correspondent, mark text/serial number, TTAB proceeding query, client name, or portfolio name to resolve.

Parameters from the server's own tool schema.

Why resolve_trademark_subject is rated Low

The tool performs entity resolution, which is a read/query operation that matches input to existing trademark records. It retrieves data without creating, modifying, or deleting anything. The authentication requirement for certain lookups slightly elevates sensitivity but does not change the fundamental read nature of the operation. Severity is low as misuse would only expose trademark entity information.

From the tool's definition 'Resolve an owner, law firm, correspondent, mark, TTAB proceeding, client, or portfolio to the best trademark entity match' — this is a lookup/resolution operation that retrieves and matches data

Questions about resolve_trademark_subject

What does the resolve_trademark_subject tool do? +

Resolve an owner, law firm, correspondent, mark, TTAB proceeding, client, or portfolio to the best trademark entity match. Resolving clients and portfolios requires authentication. 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 resolve_trademark_subject accept? +

resolve_trademark_subject accepts 3 parameters: limit, entity, subject_name. Required: entity, subject_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resolve_trademark_subject? +

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

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

Can I rate-limit resolve_trademark_subject? +

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

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

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

Across the catalogue

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