Low Risk

brand_clarify

Resolve an ambiguous brand value interactively. After brand_compile, some values need human confirmation — wrong primary color, unknown font, unassigned color roles. Pass the clarification item ID and the user's answer (hex color, role name, font name, or 'yes'/'no'). Supports natural language: '...

Part of the Brandcode MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call brand_clarify to retrieve information from Brandcode MCP 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 brand_clarify 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.

brandcode-mcp.yaml
tools:
  brand_clarify:
    rules:
      - action: allow

See the full Brandcode MCP policy for all 42 tools.

Tool Name brand_clarify
Category Read
Risk Level Low

View all 42 tools →

Agents calling read-class tools like brand_clarify have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the brand_clarify tool do? +

Resolve an ambiguous brand value interactively. After brand_compile, some values need human confirmation — wrong primary color, unknown font, unassigned color roles. Pass the clarification item ID and the user's answer (hex color, role name, font name, or 'yes'/'no'). Supports natural language: 'the purple one is accent' or '#5544f2 is secondary'. Returns updated identity and remaining clarification count.. It is categorised as a Read tool in the Brandcode MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on brand_clarify? +

Add a rule in your Intercept YAML policy under the tools section for brand_clarify. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Brandcode MCP MCP server.

What risk level is brand_clarify? +

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

Can I rate-limit brand_clarify? +

Yes. Add a rate_limit block to the brand_clarify rule in your Intercept 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_clarify completely? +

Set action: deny in the Intercept policy for brand_clarify. 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_clarify? +

brand_clarify is provided by the Brandcode MCP MCP server (@brandsystem/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Brandcode MCP

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.