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

get_firm_correspondent_tasks

Resolve a trademark law firm and return what its lawyers should focus on: overdue/next-window action-required deadlines plus recent Office Actions from both case-file events and prosecution documents, including ROA-filed and §2(d) indicators. Use this for questions like "what correspondent tasks ...

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

This record as markdown: /tools/com-gleanmark-trademark-search/get-firm-correspondent-tasks.md

What get_firm_correspondent_tasks does on GleanMark Trademark Search

AI agents call get_firm_correspondent_tasks 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
limit integer Maximum deadlines/recent OAs/task previews to return.
firm_name string Yes Law firm name or normalized key, e.g. "Imani Law" or "imanilawllp".
deadline_days integer How many days ahead to include action-required deadlines. Overdue items still in grace are also included.
recent_oa_days integer How many days back to include recent Office Actions.

Parameters from the server's own tool schema.

Why get_firm_correspondent_tasks is rated Low

Even though get_firm_correspondent_tasks 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.

Questions about get_firm_correspondent_tasks

What does the get_firm_correspondent_tasks tool do? +

Resolve a trademark law firm and return what its lawyers should focus on: overdue/next-window action-required deadlines plus recent Office Actions from both case-file events and prosecution documents, including ROA-filed and §2(d) indicators. Use this for questions like "what correspondent tasks should this firm focus on over the next 30 days?" or "what recent OAs does this law firm have?". 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 get_firm_correspondent_tasks accept? +

get_firm_correspondent_tasks accepts 4 parameters: limit, firm_name, deadline_days, recent_oa_days. Required: firm_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_firm_correspondent_tasks? +

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

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

Can I rate-limit get_firm_correspondent_tasks? +

Yes. Add a rate_limit block to the get_firm_correspondent_tasks 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 get_firm_correspondent_tasks completely? +

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

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

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