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

get_fame_profile

Get the full fame profile for a brand (by mark wording or brand stem): fame tier (broad/dilution-tier vs market-specific), the fame "path" it cleared (concentrated dominant family vs large multi-class portfolio), its famous class footprint, corporate-family portfolio size and class breadth, brand...

SERVERGleanMark Trademark Search SOURCEhttps://gleanmark.com/mcp
Low RISK CLASS
Category Read
Parameters 11 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-fame-profile.md

What get_fame_profile does on GleanMark Trademark Search

AI agents call get_fame_profile 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
mark_or_stem string Yes A mark ("THE DISNEY STORE") or a bare brand stem ("disney"). Both resolve to the same family.

Parameters from the server's own tool schema.

Why get_fame_profile is rated Low

get_fame_profile performs data retrieval and analysis only. It gathers information about trademark fame metrics, portfolio characteristics, and enforcement history to inform strategy, but does not create, modify, delete, or execute any actions. The tool is explicitly framed as providing 'circumstantial signal, not statutory fame proof', emphasizing its informational nature.

From the tool's definition Tool retrieves and analyzes existing trademark data: 'Get the full fame profile for a brand', 'fame tier', 'famous class footprint', 'corporate-family portfolio size', 'TTAB enforcement history'.

Questions about get_fame_profile

What does the get_fame_profile tool do? +

Get the full fame profile for a brand (by mark wording or brand stem): fame tier (broad/dilution-tier vs market-specific), the fame "path" it cleared (concentrated dominant family vs large multi-class portfolio), its famous class footprint, corporate-family portfolio size and class breadth, brand-stem crowding, and TTAB enforcement history. Use to explain WHY a mark is (or is not) famous, or to profile a senior mark before a §2(d) / opposition / dilution strategy. Circumstantial signal, not statutory fame proof. 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_fame_profile accept? +

get_fame_profile accepts 1 parameter: mark_or_stem. Required: mark_or_stem. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_fame_profile? +

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

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

Can I rate-limit get_fame_profile? +

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

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

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