get_owner_filing_trends
Get a trademark owner's filing trends over time — yearly filing counts broken down by Nice class. Shows how the owner's trademark portfolio has evolved.
This record as markdown: /tools/com-gleanmark-trademark-search/get-owner-filing-trends.md
What get_owner_filing_trends does on GleanMark Trademark Search
AI agents call get_owner_filing_trends 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 |
|---|---|---|---|
end_year | integer | — | End year (default: current year) |
owner_name | string | Yes | Owner name as shown in USPTO records (e.g., "NIKE, INC."). Use search_by_owner first to find the exact name. |
start_year | integer | — | Start year (default: 2000) |
Parameters from the server's own tool schema.
Why get_owner_filing_trends is rated Low
This tool queries and returns historical data without any side effects. It retrieves pre-existing statistics about trademark filing patterns, which is purely informational. The tool does not create, modify, delete, or execute any operations—it simply presents data analysis over existing USPTO trademark records.
From the tool's definition Tool retrieves historical filing trend data ('Get...filing trends over time — yearly filing counts'). No modification, deletion, or execution of external operations. Returns aggregated analytics about trademark owner portfolio evolution.
Attacks that exploit this kind of access
The rule that runs get_owner_filing_trends 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_owner_filing_trends, this is the rule to start with:
get_owner_filing_trends 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_owner_filing_trends call is checked against it from then on.
Questions about get_owner_filing_trends
Get a trademark owner's filing trends over time — yearly filing counts broken down by Nice class. Shows how the owner's trademark portfolio has evolved. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
get_owner_filing_trends accepts 3 parameters: end_year, owner_name, start_year. Required: owner_name. 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_owner_filing_trends: 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_owner_filing_trends 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_owner_filing_trends 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_owner_filing_trends. 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_owner_filing_trends 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