get_ttab_proceeding_details
Get raw details for a TTAB proceeding — parties, involved marks, counsel, and recent filings with entry numbers and working TTABVUE document links. Use get_ttab_document to read one selected filing. Use get_owner_ttab_enforcement for owner-wide distributions and analyze_ttab_proceeding for AI-pow...
This record as markdown: /tools/com-gleanmark-trademark-search/get-ttab-proceeding-details.md
What get_ttab_proceeding_details does on GleanMark Trademark Search
AI agents call get_ttab_proceeding_details 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 |
|---|---|---|---|
proceeding_number | string | Yes | TTAB proceeding number (e.g., "91284756") |
Parameters from the server's own tool schema.
Why get_ttab_proceeding_details is rated Low
This tool queries a public database (USPTO TTAB proceedings) and returns read-only information about trademark dispute details, filings, and metadata. It has no side effects, creates no data, executes nothing, and cannot modify or destroy information. The severity is low because the data returned is already public and no action can be taken through this tool alone.
From the tool's definition Tool retrieves 'raw details for a TTAB proceeding — parties, involved marks, counsel, and recent filings' and 'document links'.
Attacks that exploit this kind of access
The rule that runs get_ttab_proceeding_details 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_ttab_proceeding_details, this is the rule to start with:
get_ttab_proceeding_details 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_ttab_proceeding_details call is checked against it from then on.
Questions about get_ttab_proceeding_details
Get raw details for a TTAB proceeding — parties, involved marks, counsel, and recent filings with entry numbers and working TTABVUE document links. Use get_ttab_document to read one selected filing. Use get_owner_ttab_enforcement for owner-wide distributions and analyze_ttab_proceeding for AI-powered merits analysis. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
get_ttab_proceeding_details accepts 1 parameter: proceeding_number. Required: proceeding_number. 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_ttab_proceeding_details: 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_ttab_proceeding_details 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_ttab_proceeding_details 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_ttab_proceeding_details. 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_ttab_proceeding_details 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