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

get_correspondent_marks

Get all trademarks handled by a specific attorney/correspondent, with prosecution event counts and office action flags. Returns marks sorted by prosecution history length. Use this for attorney-specific mark queries.

SERVERGleanMark Trademark Search SOURCEhttps://gleanmark.com/mcp
Low RISK CLASS
Category Read
Parameters 70 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-correspondent-marks.md

What get_correspondent_marks does on GleanMark Trademark Search

AI agents call get_correspondent_marks 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 marks to return.
search_term string Attorney name to search for (e.g., "Todd Schneider"). Will find the best match.
status_filter string Filter marks by status.
correspondent_id string Alias for canonical_correspondent_id.
correspondent_name string Alias for search_term. Preferred when the caller already knows this is a correspondent name.
recent_window_days integer How many days back to count recent office actions. Use 90 for "last 3 months".
canonical_correspondent_id string UUID of the correspondent (from search_attorneys result). Use this if you already have the ID.

Parameters from the server's own tool schema.

Why get_correspondent_marks is rated Low

Even though get_correspondent_marks 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_correspondent_marks

What does the get_correspondent_marks tool do? +

Get all trademarks handled by a specific attorney/correspondent, with prosecution event counts and office action flags. Returns marks sorted by prosecution history length. Use this for attorney-specific mark queries. 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_correspondent_marks accept? +

get_correspondent_marks accepts 7 parameters: limit, search_term, status_filter, correspondent_id, correspondent_name, recent_window_days, canonical_correspondent_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_correspondent_marks? +

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

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

Can I rate-limit get_correspondent_marks? +

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

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

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