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

get_owner_related_parties

Find entities likely related to a trademark owner (predecessors, subsidiaries, sister companies) from USPTO evidence: shared ownership history on the same marks, shared filing addresses (agent addresses excluded), and shared distinctive name tokens. Returns evidence and a high/possible confidence...

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

This record as markdown: /tools/com-gleanmark-trademark-search/get-owner-related-parties.md

What get_owner_related_parties does on GleanMark Trademark Search

AI agents call get_owner_related_parties 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 related parties to return
owner_name string Yes Owner name as recorded at the USPTO (e.g., "Netflix, Inc."). Normalized internally to the owner key.

Parameters from the server's own tool schema.

Why get_owner_related_parties is rated Low

Even though get_owner_related_parties only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about get_owner_related_parties

What does the get_owner_related_parties tool do? +

Find entities likely related to a trademark owner (predecessors, subsidiaries, sister companies) from USPTO evidence: shared ownership history on the same marks, shared filing addresses (agent addresses excluded), and shared distinctive name tokens. Returns evidence and a high/possible confidence tier per hit — treat 'possible' as tentative. Use when analyzing an owner's full corporate family, portfolio scope, or whether two owners of similar marks are actually affiliated. Pass the owner name exactly as recorded (resolve with resolve_trademark_subject first if ambiguous). 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 get_owner_related_parties accept? +

get_owner_related_parties accepts 2 parameters: limit, owner_name. Required: owner_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_owner_related_parties? +

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

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

Can I rate-limit get_owner_related_parties? +

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

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

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