get_reference_lookup

Look up USPTO or TTAB reference codes and small lookup tables such as status codes, statement types, legal entity types, Nice classes, design codes, and TTAB proceeding/status/role codes.

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

Low RISK CLASS

Category Read

Parameters 51 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-reference-lookup.md

WHAT IT DOES

What get_reference_lookup does on GleanMark Trademark Search

AI agents call get_reference_lookup 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 code to look up when known.
`limit`	integer	—	Maximum entries to return.
`query`	string	—	Free-text search across code descriptions and labels.
`after_code`	string	—	Cursor from next_after_code for the next page when browsing a reference table without code/query filters.
`reference_type`	string	Yes	Which small lookup/reference table to search.

Parameters from the server's own tool schema.

RISK

Why get_reference_lookup is rated Low

This tool retrieves and queries reference data (codes, lookup tables, status definitions) from a static or semi-static dataset. It has no side effects, does not modify data, execute code, or perform destructive operations. It is a simple read-only lookup utility, making it a Read category tool with low severity risk.

From the tool's definition Tool description states it 'Look up USPTO or TTAB reference codes and small lookup tables such as status codes, statement types, legal entity types, Nice classes, design codes, and TTAB proceeding/status/role codes.' This is purely a lookup/retrieval…

Risk signalsAccepts freeform code/query input (code)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_reference_lookup Allowed

get_reference_lookup 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_reference_lookup": {}
  }
}

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_reference_lookup call is checked against it from then on.

FAQ

Questions about get_reference_lookup

What does the get_reference_lookup tool do? +

Look up USPTO or TTAB reference codes and small lookup tables such as status codes, statement types, legal entity types, Nice classes, design codes, and TTAB proceeding/status/role codes. 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_reference_lookup accept? +

get_reference_lookup accepts 5 parameters: code, limit, query, after_code, reference_type. Required: reference_type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_reference_lookup? +

Register the GleanMark Trademark Search MCP server in PolicyLayer and add a rule for get_reference_lookup: 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_reference_lookup? +

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

Can I rate-limit get_reference_lookup? +

Yes. Add a rate_limit block to the get_reference_lookup 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_reference_lookup completely? +

Set action: deny in the PolicyLayer policy for get_reference_lookup. 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_reference_lookup? +

get_reference_lookup 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 →