get_event_code_reference
Look up USPTO event codes used in trademark prosecution. Search by exact code, code prefix, or keyword in the event description. Returns the code, human-readable description, and category.
This record as markdown: /tools/com-gleanmark-trademark-search/get-event-code-reference.md
What get_event_code_reference does on GleanMark Trademark Search
AI agents call get_event_code_reference 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 |
|---|---|---|---|
code | string | — | Exact USPTO event code or prefix (e.g., "OAIN" for exact, "OA" for prefix match). |
limit | integer | — | Maximum number of results to return (default 20). |
search | string | — | Keyword to search in event descriptions (e.g., "office action", "abandoned"). |
Parameters from the server's own tool schema.
Why get_event_code_reference is rated Low
This tool retrieves reference data about USPTO event codes—a static, read-only lookup function. It queries a database to return codes and their descriptions without creating, modifying, deleting, or executing anything. The low severity reflects that misuse would only expose publicly available trademark prosecution reference information with no blast radius.
From the tool's definition Tool description states it 'Look[s] up USPTO event codes' and 'Returns the code, human-readable description, and category.' The verb is lookup/search with no modification capability. No arguments suggest destructive or executable operations.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs get_event_code_reference 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_event_code_reference, this is the rule to start with:
get_event_code_reference 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_event_code_reference call is checked against it from then on.
Questions about get_event_code_reference
Look up USPTO event codes used in trademark prosecution. Search by exact code, code prefix, or keyword in the event description. Returns the code, human-readable description, and category. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
get_event_code_reference accepts 3 parameters: code, limit, search. 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_event_code_reference: 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_event_code_reference 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_event_code_reference 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_event_code_reference. 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_event_code_reference 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