get_mark_deadlines

SERVERGleanMark Trademark Search SOURCEhttps://gleanmark.com/mcp

Low RISK CLASS

Category Read

Parameters 80 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-gleanmark-trademark-search/get-mark-deadlines.md

WHAT IT DOES

What get_mark_deadlines does on GleanMark Trademark Search

AI agents call get_mark_deadlines 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 number of deadline rows to return. Defaults to 50.
`days_back`	integer	—	How far back to include overdue or recently resolved deadlines. Defaults to 60 days.
`days_ahead`	integer	—	How far forward to look. Defaults to 365 days.
`subject_name`	string	—	Specific mark text or serial-number-like query. Use when the user names the mark instead of giving a serial.
`serial_number`	string	—	USPTO serial number for the specific mark.
`status_filter`	string	—	Deadline status filter. Defaults to active.
`include_opposition_period`	boolean	—	Deprecated alias for include_informational_windows. Defaults to false.
`include_informational_windows`	boolean	—	Include informational review windows such as publication opposition windows. Defaults to false.

Parameters from the server's own tool schema.

RISK

Why get_mark_deadlines is rated Low

This is a read-only query tool that retrieves publicly available trademark deadline information. It does not create, modify, delete, or execute any operations. The explicit clarification that it accesses only public, system-generated data and excludes private user data further confirms it is a safe retrieval operation with minimal blast radius if misused.

From the tool's definition Tool retrieves public trademark deadlines for a specific mark using serial number or mark name. Description explicitly states it retrieves 'public, system-generated trademark deadlines' and 'does not expose any workspace, client, reminder, or user-created…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_mark_deadlines 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_mark_deadlines, this is the rule to start with:

get_mark_deadlines Allowed

get_mark_deadlines is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_mark_deadlines": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GleanMark Trademark Search, apply this rule, and every get_mark_deadlines call is checked against it from then on.

FAQ

Questions about get_mark_deadlines

What does the get_mark_deadlines tool do? +

Get public, system-generated trademark deadlines for a specific mark. Accepts a serial number directly or resolves a mark name to a specific serial first. Does not expose any workspace, client, reminder, or user-created deadline data. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.

What parameters does get_mark_deadlines accept? +

get_mark_deadlines accepts 8 parameters: limit, days_back, days_ahead, subject_name, serial_number, status_filter, include_opposition_period, include_informational_windows. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_mark_deadlines? +

Register the GleanMark Trademark Search MCP server in PolicyLayer and add a rule for get_mark_deadlines: 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.

What risk level is get_mark_deadlines? +

get_mark_deadlines is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_mark_deadlines? +

Yes. Add a rate_limit block to the get_mark_deadlines 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.

How do I block get_mark_deadlines completely? +

Set action: deny in the PolicyLayer policy for get_mark_deadlines. 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.

What MCP server provides get_mark_deadlines? +

get_mark_deadlines 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.

KEEP EXPLORING

More on GleanMark Trademark Search, and thousands of servers like it.

This server

All 61 GleanMark Trademark Search tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →