webcontext_brand
Extract public brand identity for a site Lightweight brand snapshot for one site URL: logos, colors, fonts, and basic public metadata. Prefer brand_retrieve for a fuller normalized brand profile or brand_search for fuzzy company-name discovery. HTTP: GET /v1/webcontext/brand
This record as markdown: /tools/com-replynodes-mcp/webcontext-brand.md
What webcontext_brand does on ReplyNodes
AI agents call webcontext_brand 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 | Yes | Target URL to fetch. Rejected if it is malformed, uses a disallowed scheme, or resolves to a private/loopback/link-local/cloud-metadata address. |
Parameters from the server's own tool schema.
Why webcontext_brand is rated Low
Retrieves publicly available brand information from a website; no side effects or data modification.
From the tool's definition Extract public brand identity, logos, colors, fonts, basic public metadata.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs webcontext_brand 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 webcontext_brand, this is the rule to start with:
webcontext_brand 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 webcontext_brand call is checked against it from then on.
Questions about webcontext_brand
Extract public brand identity for a site Lightweight brand snapshot for one site URL: logos, colors, fonts, and basic public metadata. Prefer brand_retrieve for a fuller normalized brand profile or brand_search for fuzzy company-name discovery. HTTP: GET /v1/webcontext/brand. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.
webcontext_brand accepts 1 parameter: url. Required: url. 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 webcontext_brand: 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.
webcontext_brand 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 webcontext_brand 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 webcontext_brand. 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.
webcontext_brand 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