get_event_status_mapping
Look up which USPTO status code and status definition most commonly follow a specific prosecution event code.
This record as markdown: /tools/com-gleanmark-trademark-search/get-event-status-mapping.md
What get_event_status_mapping does on GleanMark Trademark Search
AI agents call get_event_status_mapping 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 | — | Maximum mappings to return. |
event_code | string | Yes | USPTO event code to inspect. |
Parameters from the server's own tool schema.
Why get_event_status_mapping is rated Low
This is a read-only query tool that retrieves and maps existing USPTO data. It queries relationships between event codes and status definitions without creating, modifying, deleting, executing code, or engaging in financial transactions. The low severity reflects that misuse would only expose trademark prosecution analytics data without operational impact.
From the tool's definition Tool 'get_event_status_mapping' performs a lookup operation to retrieve status code definitions and their relationships following prosecution event codes.
Attacks that exploit this kind of access
The rule that runs get_event_status_mapping 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_status_mapping, this is the rule to start with:
get_event_status_mapping 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_status_mapping call is checked against it from then on.
Questions about get_event_status_mapping
Look up which USPTO status code and status definition most commonly follow a specific prosecution event code. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
get_event_status_mapping accepts 2 parameters: limit, event_code. Required: event_code. 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_status_mapping: 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_status_mapping 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_status_mapping 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_status_mapping. 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_status_mapping 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