get_deadline_satisfaction_mapping
Check whether a specific USPTO event code satisfies a specific deadline type such as office action response, opposition period, Section 8, or Section 15.
This record as markdown: /tools/com-gleanmark-trademark-search/get-deadline-satisfaction-mapping.md
What get_deadline_satisfaction_mapping does on GleanMark Trademark Search
AI agents call get_deadline_satisfaction_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 |
|---|---|---|---|
event_code | string | Yes | USPTO event code to inspect. |
deadline_type | string | Yes | Deadline family to test against. |
Parameters from the server's own tool schema.
Why get_deadline_satisfaction_mapping is rated Low
This tool queries USPTO deadline data to determine compliance or relationship information between event codes and deadline types. It performs a read-only lookup operation with no side effects—it does not modify data, execute external code, delete records, or commit financial transactions.
From the tool's definition The tool 'get_deadline_satisfaction_mapping' retrieves and checks whether event codes satisfy specific deadline types.
Attacks that exploit this kind of access
The rule that runs get_deadline_satisfaction_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_deadline_satisfaction_mapping, this is the rule to start with:
get_deadline_satisfaction_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_deadline_satisfaction_mapping call is checked against it from then on.
Questions about get_deadline_satisfaction_mapping
Check whether a specific USPTO event code satisfies a specific deadline type such as office action response, opposition period, Section 8, or Section 15. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
get_deadline_satisfaction_mapping accepts 2 parameters: event_code, deadline_type. Required: event_code, deadline_type. 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_deadline_satisfaction_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_deadline_satisfaction_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_deadline_satisfaction_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_deadline_satisfaction_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_deadline_satisfaction_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