get_top_filers
Get a ranked filer table for a date range, filer type, and optional Nice classes. Use this when the user asks for top filers, top owners, top law firms, or top correspondents by class or date, such as "Who are the top 10 filers in Class 9 in 2025?" Returns the ranked rows with per-filer live, reg...
This record as markdown: /tools/com-gleanmark-trademark-search/get-top-filers.md
What get_top_filers does on GleanMark Trademark Search
AI agents call get_top_filers 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 |
|---|---|---|---|
limit | integer | — | Maximum number of ranked filers to return. |
end_date | string | Yes | Inclusive end date in YYYY-MM-DD format. |
filer_type | string | — | Whether to rank owners, law firms, or individual correspondents. |
start_date | string | Yes | Inclusive start date in YYYY-MM-DD format. |
nice_classes | array | — | Optional Nice classes to filter by. Use integers like 42 or 9. |
Parameters from the server's own tool schema.
Why get_top_filers is rated Low
Even though get_top_filers only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_top_filers 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_top_filers, this is the rule to start with:
get_top_filers 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_top_filers call is checked against it from then on.
Questions about get_top_filers
Get a ranked filer table for a date range, filer type, and optional Nice classes. Use this when the user asks for top filers, top owners, top law firms, or top correspondents by class or date, such as "Who are the top 10 filers in Class 9 in 2025?" Returns the ranked rows with per-filer live, registered, and pending counts plus corpus totals. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
get_top_filers accepts 5 parameters: limit, end_date, filer_type, start_date, nice_classes. Required: end_date, start_date. 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_top_filers: 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_top_filers 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_top_filers 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_top_filers. 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_top_filers 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