Low Risk

brand_get

Get full brand details (colors + typography)

How to control brand_get ↓

What brand_get does on BWVI

AI agents call brand_get 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 brand_get needs a policy

This tool retrieves brand information (colors and typography) without creating, modifying, deleting, or executing any operations. The 'get' verb and read-only nature of fetching existing brand details classify it as a Read operation with low severity, as disclosure of design system parameters poses minimal risk.

From the tool's definition Tool name 'brand_get' and description 'Get full brand details (colors + typography)' indicate retrieval of existing data with no modification or side effects.

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

How to control brand_get

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 brand_get:

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

brand_get 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 brand_get

What does the brand_get tool do? +

Get full brand details (colors + typography). 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 brand_get? +

Register the BWVI MCP server in PolicyLayer and add a rule for brand_get: 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 brand_get? +

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

Can I rate-limit brand_get? +

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

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

brand_get 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.