get_correspondent_specialization
Summarize what a named correspondent specializes in, including top clients, top Nice classes, and prosecution-versus-TTAB profile. Use this when the user asks what a specific correspondent or attorney specializes in.
This record as markdown: /tools/com-gleanmark-trademark-search/get-correspondent-specialization.md
What get_correspondent_specialization does on GleanMark Trademark Search
AI agents call get_correspondent_specialization 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 |
|---|---|---|---|
url_key | string | — | Known correspondent url_key, if already resolved. |
search_term | string | — | Correspondent or attorney name to resolve. |
top_class_limit | integer | — | Maximum top Nice classes to return. |
top_client_limit | integer | — | Maximum top clients to return. |
correspondent_name | string | — | Alias for search_term. |
Parameters from the server's own tool schema.
Why get_correspondent_specialization is rated Low
Even though get_correspondent_specialization 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 get_correspondent_specialization 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_correspondent_specialization, this is the rule to start with:
get_correspondent_specialization 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_correspondent_specialization call is checked against it from then on.
Questions about get_correspondent_specialization
Summarize what a named correspondent specializes in, including top clients, top Nice classes, and prosecution-versus-TTAB profile. Use this when the user asks what a specific correspondent or attorney specializes in. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
get_correspondent_specialization accepts 5 parameters: url_key, search_term, top_class_limit, top_client_limit, correspondent_name. 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_correspondent_specialization: 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_correspondent_specialization 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_correspondent_specialization 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_correspondent_specialization. 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_correspondent_specialization 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