count_trademarks_by_attributes

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

Low RISK CLASS

Category Read

Parameters 90 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-gleanmark-trademark-search/count-trademarks-by-attributes.md

WHAT IT DOES

What count_trademarks_by_attributes does on GleanMark Trademark Search

AI agents call count_trademarks_by_attributes 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	—
`mark_types`	array	—
`nice_classes`	array	—
`status_filter`	string	—	Use registered for currently live registrations; live also includes pending applications.
`class_match_mode`	string	—
`color_match_mode`	string	—	all permits additional claimed colors; only requires exactly the selected colors; only_bw also permits black/white.
`standard_characters`	boolean	—
`claimed_color_shades`	array	—	Exact canonical shades from the USPTO color claim.
`claimed_color_families`	array	—	Normalized color families. Burgundy and maroon, for example, count as red.

Parameters from the server's own tool schema.

RISK

Why count_trademarks_by_attributes is rated Low

Even though count_trademarks_by_attributes only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

count_trademarks_by_attributes Allowed

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

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

FAQ

Questions about count_trademarks_by_attributes

What does the count_trademarks_by_attributes tool do? +

Count and preview USPTO marks by record attributes rather than owner identity, with mark-type, standard-character, and Nice-class breakdowns plus metadata coverage. Use this for drawing type, standard-character, Nice-class, status, and cross-attribute counts. It can intersect claimed-color criteria with those attributes; color-only counts, rankings, lists, and vocabulary are outside its scope. 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 count_trademarks_by_attributes accept? +

count_trademarks_by_attributes accepts 9 parameters: limit, mark_types, nice_classes, status_filter, class_match_mode, color_match_mode, standard_characters, claimed_color_shades, claimed_color_families. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on count_trademarks_by_attributes? +

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

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

Can I rate-limit count_trademarks_by_attributes? +

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

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

count_trademarks_by_attributes 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

The MCP Attack Database →

Guides

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