count_filings_by_period
Counts U.S. trademark applications filed across the whole register in a date range, grouped by calendar year, month or day, with each period split into U.S.-filed and Madrid Protocol (79-series) applications and the change from the previous period. Answers questions such as how many trademark app...
This record as markdown: /tools/com-gleanmark-trademark-search/count-filings-by-period.md
What count_filings_by_period does on GleanMark Trademark Search
AI agents call count_filings_by_period 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_date | string | Yes | Last filing date to count, YYYY-MM-DD, inclusive (e.g. 2025-12-31). |
group_by | string | — | Period size. Daily counts cover at most about a year. |
start_date | string | Yes | First filing date to count, YYYY-MM-DD (e.g. 2024-01-01). |
Parameters from the server's own tool schema.
Why count_filings_by_period is rated Low
Even though count_filings_by_period 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 count_filings_by_period 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 count_filings_by_period, this is the rule to start with:
count_filings_by_period 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 count_filings_by_period call is checked against it from then on.
Questions about count_filings_by_period
Counts U.S. trademark applications filed across the whole register in a date range, grouped by calendar year, month or day, with each period split into U.S.-filed and Madrid Protocol (79-series) applications and the change from the previous period. Answers questions such as how many trademark applications were filed in 2025 and how that compares with 2024, or which month of a year had the most filings. Counts are one per serial number by the filing date on the USPTO record; they are calendar periods, not USPTO fiscal-year statistics, and not class counts. Returns data_through, the latest filing date on the register; recent periods grow as late records arrive. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
count_filings_by_period accepts 3 parameters: end_date, group_by, start_date. 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 count_filings_by_period: 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.
count_filings_by_period 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 count_filings_by_period 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 count_filings_by_period. 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.
count_filings_by_period 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