is_mark_famous
Check whether a trademark is FAMOUS — and, critically, famous FOR A SPECIFIC MARKET (you pass the applicant's Nice class as a PROXY for that market; fame is market-determined, there is no per-class fame doctrine). Fame is market-specific (Joseph Phelps Vineyards v. Fairmont): a mark famous for el...
This record as markdown: /tools/com-gleanmark-trademark-search/is-mark-famous.md
What is_mark_famous does on GleanMark Trademark Search
AI agents call is_mark_famous 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 | string | Yes | The mark wording to check (e.g. "MONSTER", "DELTA", "APPLE"). |
class | string | — | Optional Nice class number 1-45 (e.g. "25"), used as a proxy for the relevant market to test market-specific fame. Omit for a class-agnostic read. |
Parameters from the server's own tool schema.
Why is_mark_famous is rated Low
is_mark_famous retrieves and queries trademark data from the USPTO database to determine fame status and related analytics. It returns informational results without side effects. This is purely a Read operation—searching and retrieving existing data. The low severity reflects minimal risk if misused; an AI agent querying trademark fame status causes no harm to systems, data integrity, or financial obligations.
From the tool's definition Tool performs queries and retrieval: 'Check whether a trademark is FAMOUS', returns analysis data ('is_famous', 'famous_in_class', 'fame tier', 'famous market footprint', 'portfolio size', 'enforcement history').
Attacks that exploit this kind of access
The rule that runs is_mark_famous 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 is_mark_famous, this is the rule to start with:
is_mark_famous 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 is_mark_famous call is checked against it from then on.
Questions about is_mark_famous
Check whether a trademark is FAMOUS — and, critically, famous FOR A SPECIFIC MARKET (you pass the applicant's Nice class as a PROXY for that market; fame is market-determined, there is no per-class fame doctrine). Fame is market-specific (Joseph Phelps Vineyards v. Fairmont): a mark famous for electronics is not automatically famous for fresh fruit. Returns is_famous, famous_in_class, the fame tier (broad/dilution-tier household name vs market-specific), the famous market footprint (expressed as Nice classes), portfolio size, and the corporate family's TTAB-as-plaintiff enforcement history. Use for "is X a famous trademark?", "is X famous for <goods>?", gauging a senior mark's §2(d) strength, or §43(c) dilution eligibility. It is a 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.
is_mark_famous accepts 2 parameters: mark, class. Required: mark. 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 is_mark_famous: 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.
is_mark_famous 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 is_mark_famous 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 is_mark_famous. 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.
is_mark_famous 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