get_prosecution_timeline
Get the prosecution timeline for a trademark — chronological list of office actions, responses, and key events (publication, registration, suspension, etc.). Raw data without AI analysis.
This record as markdown: /tools/com-gleanmark-trademark-search/get-prosecution-timeline.md
What get_prosecution_timeline does on GleanMark Trademark Search
AI agents call get_prosecution_timeline 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 |
|---|---|---|---|
serial_number | string | Yes | USPTO serial number |
Parameters from the server's own tool schema.
Why get_prosecution_timeline is rated Low
This tool retrieves historical prosecution data from the USPTO trademark database. It is a straightforward query operation that returns read-only information about the timeline and status of trademark applications. There are no side effects, no data modification, and no capability to execute actions or incur costs.
From the tool's definition Tool returns 'chronological list of office actions, responses, and key events' and explicitly states 'Raw data without AI analysis.' No creation, modification, deletion, code execution, or financial impact.
Attacks that exploit this kind of access
The rule that runs get_prosecution_timeline 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_prosecution_timeline, this is the rule to start with:
get_prosecution_timeline 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_prosecution_timeline call is checked against it from then on.
Questions about get_prosecution_timeline
Get the prosecution timeline for a trademark — chronological list of office actions, responses, and key events (publication, registration, suspension, etc.). Raw data without AI analysis. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
get_prosecution_timeline accepts 1 parameter: serial_number. Required: serial_number. 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_prosecution_timeline: 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_prosecution_timeline 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_prosecution_timeline 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_prosecution_timeline. 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_prosecution_timeline 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