Low Risk

list_brands

Search/list 115 built-in brand systems

How to control list_brands ↓

What list_brands does on BWVI

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

Low Risk

Why list_brands needs a policy

This tool retrieves or lists existing brand system data without creating, modifying, deleting, or executing operations. The verbs 'search' and 'list' are typical Read operations. No destructive, financial, or code execution capabilities are present. Severity is low because listing brand systems has minimal blast radius—worst case, an AI agent would retrieve design metadata.

From the tool's definition Tool name 'list_brands' and description 'Search/list 115 built-in brand systems' indicate a query/retrieval operation with no modification or side effects.

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

How to control list_brands

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

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

list_brands 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 BWVI — 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 list_brands

What does the list_brands tool do? +

Search/list 115 built-in brand systems. It is categorised as a Read tool in the BWVI MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_brands? +

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

What risk level is list_brands? +

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

Can I rate-limit list_brands? +

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

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

list_brands is provided by the BWVI MCP server (lh123aa/bwvi-design). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BWVI tool call.

Start from BWVI, 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.

15 BWVI 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.