get_trademark_analytics
Get aggregate statistics about USPTO trademark filings, registrations, and TTAB proceedings.
This record as markdown: /tools/com-gleanmark-trademark-search/get-trademark-analytics.md
What get_trademark_analytics does on GleanMark Trademark Search
AI agents call get_trademark_analytics 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 |
|---|---|---|---|
metric | string | Yes | Type of analytics to query |
end_date | string | — | End date for custom period (YYYY-MM-DD) |
group_by | string | — | |
nice_class | integer | — | |
start_date | string | — | Start date for custom period (YYYY-MM-DD) |
time_period | string | — |
Parameters from the server's own tool schema.
Why get_trademark_analytics is rated Low
The tool performs a pure data retrieval and aggregation function on USPTO trademark records. Aggregate statistics are read-only queries that do not modify data, execute code, delete records, or trigger financial transactions.
From the tool's definition Tool description states 'Get aggregate statistics about USPTO trademark filings, registrations, and TTAB proceedings' — this retrieves and aggregates existing public data with no modification, creation, deletion, or external operation.
Attacks that exploit this kind of access
The rule that runs get_trademark_analytics 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_trademark_analytics, this is the rule to start with:
get_trademark_analytics 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_trademark_analytics call is checked against it from then on.
Questions about get_trademark_analytics
Get aggregate statistics about USPTO trademark filings, registrations, and TTAB proceedings. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
get_trademark_analytics accepts 6 parameters: metric, end_date, group_by, nice_class, start_date, time_period. Required: metric. 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_trademark_analytics: 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_trademark_analytics 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_trademark_analytics 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_trademark_analytics. 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_trademark_analytics 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