check_brand_availability
Quick brand availability check — combines domain availability with a trademark conflict signal. Returns a recommendation tier (avoid, probably avoid, promising, or no conflicts found). Good first step before a full clearance search.
This record as markdown: /tools/com-gleanmark-trademark-search/check-brand-availability.md
What check_brand_availability does on GleanMark Trademark Search
AI agents call check_brand_availability 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 |
|---|---|---|---|
brand_name | string | Yes | Brand name to check |
industries | array | — | Industry categories |
nice_classes | array | — | Nice classes to check against |
business_description | string | — | Brief description of the business |
Parameters from the server's own tool schema.
Why check_brand_availability is rated Low
This tool retrieves and analyzes existing data (domain availability status and trademark conflict signals) to produce a recommendation. It has no side effects—it does not create, modify, delete, or execute operations. It is a preliminary read operation that precedes full clearance searches, analogous to a search or lookup query.
From the tool's definition Tool performs a 'quick brand availability check' that 'combines domain availability with a trademark conflict signal' and 'returns a recommendation tier'.
Attacks that exploit this kind of access
The rule that runs check_brand_availability 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 check_brand_availability, this is the rule to start with:
check_brand_availability 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 check_brand_availability call is checked against it from then on.
Questions about check_brand_availability
Quick brand availability check — combines domain availability with a trademark conflict signal. Returns a recommendation tier (avoid, probably avoid, promising, or no conflicts found). Good first step before a full clearance search. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
check_brand_availability accepts 4 parameters: brand_name, industries, nice_classes, business_description. Required: brand_name. 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 check_brand_availability: 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.
check_brand_availability 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 check_brand_availability 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 check_brand_availability. 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.
check_brand_availability 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