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...
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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'.
Attacks that exploit this kind of access
The rule that runs get_fame_profile 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 get_fame_profile, this is the rule to start with:
get_fame_profile 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 get_fame_profile call is checked against it from then on.
Questions about 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-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.
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.
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.
get_fame_profile 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 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.
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.
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.
This server
Across the catalogue