get_class_relationships
Look up coordinated Nice classes or related Nice classes for a given class number.
This record as markdown: /tools/com-gleanmark-trademark-search/get-class-relationships.md
What get_class_relationships does on GleanMark Trademark Search
AI agents call get_class_relationships 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 rows to return. |
class_number | integer | Yes | Nice class number to inspect. |
include_legacy | boolean | — | Include legacy US classes A, B, and 200 when returning coordinated classes. |
relationship_type | string | — | Whether to return USPTO coordinated classes or curated related classes. |
Parameters from the server's own tool schema.
Why get_class_relationships is rated Low
This tool retrieves trademark classification metadata (Nice classes) from the GleanMark database. It performs a simple lookup query that returns structured data about trademark class relationships. There are no side effects, no data creation or modification, no code execution, and no destructive operations.
From the tool's definition Tool description states 'Look up' which is a retrieval operation. The function returns coordinated or related Nice classification data with no mutations, deletions, or external operations triggered.
Attacks that exploit this kind of access
The rule that runs get_class_relationships 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_class_relationships, this is the rule to start with:
get_class_relationships 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_class_relationships call is checked against it from then on.
Questions about get_class_relationships
Look up coordinated Nice classes or related Nice classes for a given class number. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
get_class_relationships accepts 4 parameters: limit, class_number, include_legacy, relationship_type. Required: class_number. 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_class_relationships: 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_class_relationships 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_class_relationships 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_class_relationships. 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_class_relationships 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