AI agents call get_brand_profile to retrieve information from Raven without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Brand profile ID. |
Parameters from the server's own tool schema.
This tool retrieves design/brand data (a profile) without modifying, deleting, or executing any operations. It is a straightforward data retrieval function with minimal blast radius even if invoked incorrectly by an AI agent.
From the tool's definition Tool name is 'get_brand_profile' and description explicitly states 'Read a local Raven creative brand profile by ID'. The verb 'Read' and retrieval of a profile by ID indicate a query operation with no side effects.
Attacks that exploit this kind of access
Read a local Raven creative brand profile by ID. It is categorised as a Read tool in the Raven MCP Server, which means it retrieves data without modifying state.
get_brand_profile accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Raven MCP server in PolicyLayer and add a rule for get_brand_profile: 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 Raven. Nothing to install.
get_brand_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_brand_profile 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.
Set action: deny in the PolicyLayer policy for get_brand_profile. 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.
get_brand_profile is provided by the Raven MCP server (raven-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_brand_profile is one line of Raven's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →