Low Risk

get_brand

get_brand

How to control get_brand ↓

What get_brand does on urlDNA MCP Server

AI agents call get_brand to retrieve information from urlDNA MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_brand needs a policy

Although the description is empty (lowering confidence slightly), the naming convention and contextual placement among other read-oriented tools strongly indicate this retrieves or queries brand information from the threat intelligence platform. No side effects or modifications are implied.

From the tool's definition Tool name 'get_brand' follows a read-like pattern (get_*), and the server context shows it operates within urlDNA's threat intelligence platform. Sibling tools include 'list_brands', 'get_query', and 'get_scan', which are all read operations.

Documented attack patterns abuse exactly the kind of access get_brand gives an agent:

How to control get_brand

PolicyLayer is an MCP gateway — it sits between your AI agents and urlDNA MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_brand:

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

get_brand is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register urlDNA MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_brand

What does the get_brand tool do? +

get_brand. It is categorised as a Read tool in the urlDNA MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_brand? +

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

What risk level is get_brand? +

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

Can I rate-limit get_brand? +

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

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

get_brand is provided by the urlDNA MCP Server MCP server (urldna/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every urlDNA MCP Server tool call.

Start from urlDNA MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 urlDNA MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.