brand_retrieve
Retrieve Brand Resolve the full brand profile of a company by domain, or extract brand details from one specific page URL: name, description, primary logo, logos, colors, fonts, social links, favicon, and og_image. HTTP: GET /v1/brand/retrieve
This record as markdown: /tools/com-replynodes-mcp/brand-retrieve.md
What brand_retrieve does on ReplyNodes
AI agents call brand_retrieve to retrieve information from ReplyNodes without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | One specific page URL to extract brand details from instead of the whole domain. |
domain | string | — | Company domain to resolve, e.g. apple.com. One of domain or url is required. |
Parameters from the server's own tool schema.
Why brand_retrieve is rated Low
Retrieves publicly available brand information without modifying data or executing operations.
From the tool's definition Retrieve brand profile, extract brand details, logos, colors, fonts, social links
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs brand_retrieve safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ReplyNodes, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For brand_retrieve, this is the rule to start with:
brand_retrieve is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ReplyNodes, apply this rule, and every brand_retrieve call is checked against it from then on.
Questions about brand_retrieve
Retrieve Brand Resolve the full brand profile of a company by domain, or extract brand details from one specific page URL: name, description, primary logo, logos, colors, fonts, social links, favicon, and og_image. HTTP: GET /v1/brand/retrieve. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.
brand_retrieve accepts 2 parameters: url, domain. The full parameter table on this page comes from the server's own tool schema.
Register the ReplyNodes MCP server in PolicyLayer and add a rule for brand_retrieve: 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 ReplyNodes. Nothing to install.
brand_retrieve 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 brand_retrieve 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 brand_retrieve. 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.
brand_retrieve is provided by the ReplyNodes MCP server (https://mcp.replynodes.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ReplyNodes, and thousands of servers like it.
This server
Across the catalogue