agentbrush_populate_identity
Auto-populate the project brand identity table from 1-3 inspiration URLs. Two modes: plan and apply. Plan mode (call without extractions): Returns a structured plan listing the URLs and the exact screenshot paths to save. The MCP does NOT crawl URLs itself — your browser/screenshot tools (Playwri...
This record as markdown: /tools/dev-agentbrush-mcp-server/agentbrush-populate-identity.md
What agentbrush_populate_identity does on Mcp Server
AI agents use agentbrush_populate_identity to create or update resources in Mcp Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
urls | array | Yes | Inspiration URLs to crawl (1-3). Only http:// and https:// are accepted. The MCP does not crawl these itself — it returns instructions for your browser/screensh |
extractions | array | — | Optional. Omit on the first call to receive a crawl plan. After your browser tools have taken screenshots and analysed them, call again with extractions to merg |
Parameters from the server's own tool schema.
Why agentbrush_populate_identity is rated Medium
This tool writes/modifies project brand identity data by populating and merging extracted design attributes (colors, style, mood) into a project configuration. It is reversible in principle (brand identity can be overwritten again), so Write is the appropriate category rather than Destructive. Severity is medium because misconfigured brand identity could propagate incorrect branding across all generated assets.
From the tool's definition Auto-populate the project brand identity table from 1-3 inspiration URLs... Apply mode: merges your findings into .a[gent config/project]
Risk signalsAccepts URL/endpoint input (extractions[].url)
Attacks that exploit this kind of access
The rule that runs agentbrush_populate_identity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agentbrush_populate_identity, this is the rule to start with:
agentbrush_populate_identity stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Server, apply this rule, and every agentbrush_populate_identity call is checked against it from then on.
Questions about agentbrush_populate_identity
Auto-populate the project brand identity table from 1-3 inspiration URLs. Two modes: plan and apply. Plan mode (call without extractions): Returns a structured plan listing the URLs and the exact screenshot paths to save. The MCP does NOT crawl URLs itself — your browser/screenshot tools (Playwright, Chrome devtools, vision API, etc.) execute the plan. Apply mode (call with extractions): After your tools have taken screenshots and analysed them for dominant colors, visual style, and mood, call this tool again with the same urls plus an extractions array. The tool merges your findings into .agentbrush/identity.json without overwriting existing data. Save screenshots EXACTLY at the paths returned by plan mode — the apply step validates each path resolves inside .agentbrush/references/ and rejects symlinks or escapes. Workflow: 1) Call this tool with { urls: [...] } to get the plan. 2) Use your own browser/screenshot tools to capture and analyse each URL. 3) Call this tool again with { urls: [...], extractions: [...] } to merge. For URLs that fail to crawl, include them in extractions with { failed: true, failure_reason: "..." }. Partial results are accepted — successful URLs are merged and failed URLs are reported. Maximum 3 URLs per call. Only http:// and https:// are accepted. Color palette caps at 8 entries; mood tags cap at 10. Existing brand identity content is preserved (merge semantics, not overwrite). It is categorised as a Write tool in the Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
agentbrush_populate_identity accepts 2 parameters: urls, extractions. Required: urls. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for agentbrush_populate_identity: 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 Mcp Server. Nothing to install.
agentbrush_populate_identity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the agentbrush_populate_identity 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 agentbrush_populate_identity. 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.
agentbrush_populate_identity is provided by the Mcp Server MCP server (@agentbrush/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue