# 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).

Agent View of the PolicyLayer registry record for `agentbrush_populate_identity`. HTML page: https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-populate-identity

## Facts

- Tool: `agentbrush_populate_identity`
- Server: Mcp Server (`@agentbrush/mcp-server`) — https://policylayer.com/tools/dev-agentbrush-mcp-server.md
- Install: `npx -y @agentbrush/mcp-server`
- Homepage: https://www.npmjs.com/package/@agentbrush/mcp-server
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| 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 | no | 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "agentbrush_populate_identity",
    "arguments": {
      "urls": []
    }
  }
}
```

## 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 own definition: "Auto-populate the project brand identity table from 1-3 inspiration URLs... Apply mode: merges your findings into .a[gent config/project]"

Risk signals: Accepts URL/endpoint input (extractions[].url)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "agentbrush_populate_identity": {
      "limits": [
        {
          "counter": "agentbrush_populate_identity_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Server (11)

- `agentbrush_remove_background` — Destructive — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-remove-background.md
- `agentbrush_edit_mask` — Execute — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-edit-mask.md
- `agentbrush_edit_mask_open` — Execute — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-edit-mask-open.md
- `agentbrush_check_status` — Read — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-check-status.md
- `agentbrush_list_presets` — Read — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-list-presets.md
- `agentbrush_list_references` — Read — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-list-references.md
- `agentbrush_edit_mask_result` — Write — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-edit-mask-result.md
- `agentbrush_generate` — Write — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-generate.md
- `agentbrush_init` — Write — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-init.md
- `agentbrush_login` — Write — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-login.md
- `agentbrush_save_as_reference` — Write — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-save-as-reference.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-agentbrush-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-agentbrush-mcp-server
