New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

analyze_prosecution_history

Analyze the full prosecution history of a trademark — narrative timeline of office actions, responses, examiner decisions, and current status, with examiner-behavior patterns. For authenticated users this launches asynchronously (usually done in under a minute; longer for large file histories) an...

SERVERGleanMark Trademark Search SOURCEhttps://gleanmark.com/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-gleanmark-trademark-search/analyze-prosecution-history.md

What analyze_prosecution_history does on GleanMark Trademark Search

AI agents call analyze_prosecution_history 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.

ParameterTypeRequiredDescription
serial_number string Yes USPTO serial number

Parameters from the server's own tool schema.

Why analyze_prosecution_history is rated Low

This tool performs read-only data retrieval and analysis of USPTO trademark prosecution records. While it may involve some computational analysis, it has no side effects—it neither modifies trademark records, deletes data, executes code with external consequences, nor involves financial transactions. The asynchronous processing is internal analysis only.

From the tool's definition Tool retrieves and analyzes existing trademark prosecution history data: 'narrative timeline of office actions, responses, examiner decisions, and current status.' The description emphasizes querying and returning analysis of historical records.

Questions about analyze_prosecution_history

What does the analyze_prosecution_history tool do? +

Analyze the full prosecution history of a trademark — narrative timeline of office actions, responses, examiner decisions, and current status, with examiner-behavior patterns. For authenticated users this launches asynchronously (usually done in under a minute; longer for large file histories) and returns a processing handle — then call get_prosecution_history_status to fetch the completed result. Tell the user it is running. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.

What parameters does analyze_prosecution_history accept? +

analyze_prosecution_history accepts 1 parameter: serial_number. Required: serial_number. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on analyze_prosecution_history? +

Register the GleanMark Trademark Search MCP server in PolicyLayer and add a rule for analyze_prosecution_history: 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.

What risk level is analyze_prosecution_history? +

analyze_prosecution_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit analyze_prosecution_history? +

Yes. Add a rate_limit block to the analyze_prosecution_history 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.

How do I block analyze_prosecution_history completely? +

Set action: deny in the PolicyLayer policy for analyze_prosecution_history. 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.

What MCP server provides analyze_prosecution_history? +

analyze_prosecution_history 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GleanMark Trademark Search's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.