Low Risk

get_trademark_by_registration

Look up a US trademark by registration number. Returns status, owner, mark text, goods/services, and classification. Requires USPTO API key.

Risk signalsHandles credentials or secrets (api_key)

Part of the Trademarks server.

get_trademark_by_registration is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TRADEMARKS →

Free to start. No card required.

AI agents call get_trademark_by_registration to retrieve information from Trademarks without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_trademark_by_registration only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_trademark_by_registration": {}
  }
}

See the full Trademarks policy for all 23 tools.

Get this rule live on your own Trademarks server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TRADEMARKS →

View all 23 tools →

These attack patterns abuse exactly the kind of access get_trademark_by_registration gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_trademark_by_registration only ever does what you allow.

SECURE TRADEMARKS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_trademark_by_registration tool do? +

Look up a US trademark by registration number. Returns status, owner, mark text, goods/services, and classification. Requires USPTO API key.. It is categorised as a Read tool in the Trademarks MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_trademark_by_registration? +

Register the Trademarks MCP server in PolicyLayer and add a rule for get_trademark_by_registration: 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 Trademarks. Nothing to install.

What risk level is get_trademark_by_registration? +

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

Can I rate-limit get_trademark_by_registration? +

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

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

get_trademark_by_registration is provided by the Trademarks MCP server (https://gateway.pipeworx.io/trademarks/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Trademarks tool call.

Deterministic rules across all 23 Trademarks tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.