search_ttab_proceedings
Search TTAB proceedings using the same discovery index as the GleanMark TTAB workspace. Use for broad proceeding discovery by party name, exact 8-digit proceeding number, 8-digit trademark serial number, or 7-digit registration number. Supports status, proceeding type, matched party role, and own...
This record as markdown: /tools/com-gleanmark-trademark-search/search-ttab-proceedings.md
What search_ttab_proceedings does on GleanMark Trademark Search
AI agents call search_ttab_proceedings 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 |
|---|---|---|---|
limit | integer | — | |
query | string | Yes | Party name, 8-digit proceeding/serial number, or 7-digit registration number. |
role_filter | array | — | Role of the party matched by query: P for plaintiff/petitioner, D for defendant/respondent. |
type_filter | array | — | Exact TTAB type labels, such as Oppositions, Cancellations, or Extensions of Time to Oppose. |
status_filter | array | — | |
owner_contains | string | — | Optional additional substring that must appear in any party name. |
Parameters from the server's own tool schema.
Why search_ttab_proceedings is rated Low
This tool retrieves and queries publicly available trademark legal proceeding data from USPTO records. It performs read-only discovery and filtering operations without creating, modifying, deleting, or executing any actions. The data returned are factual legal records. No side effects or irreversible changes occur from its use.
From the tool's definition 'Search TTAB proceedings' using discovery index by party name, proceeding number, serial number, registration number with filters for status and proceeding type. No modification, deletion, or execution of external operations described.
Attacks that exploit this kind of access
The rule that runs search_ttab_proceedings 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 search_ttab_proceedings, this is the rule to start with:
search_ttab_proceedings 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 search_ttab_proceedings call is checked against it from then on.
Questions about search_ttab_proceedings
Search TTAB proceedings using the same discovery index as the GleanMark TTAB workspace. Use for broad proceeding discovery by party name, exact 8-digit proceeding number, 8-digit trademark serial number, or 7-digit registration number. Supports status, proceeding type, matched party role, and owner-name filters. For one known case after discovery, use get_ttab_proceeding_details; for owner enforcement statistics, use get_owner_ttab_enforcement. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
search_ttab_proceedings accepts 6 parameters: limit, query, role_filter, type_filter, status_filter, owner_contains. Required: query. 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 search_ttab_proceedings: 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.
search_ttab_proceedings 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 search_ttab_proceedings 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 search_ttab_proceedings. 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.
search_ttab_proceedings 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