# search_icons

Finds appropriate Material Design icons matching keywords that describe their usage, style, or shape.

Agent View of the PolicyLayer registry record for `search_icons`. HTML page: https://policylayer.com/tools/com-googleapis-design-mcp/search-icons

## Facts

- Tool: `search_icons`
- Server: Mcp (`https://design.googleapis.com/mcp`) — https://policylayer.com/tools/com-googleapis-design-mcp.md
- Homepage: https://github.com/https://design.googleapis.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `tags` | array | yes | Required. A list of semantic keywords or metadata tags that describe the desired icon's visual or functional properties. If possible, specify at least three tag |
| `iconSet` | string | no | Optional. The icon set to search within (e.g., "Material Symbols", "Material Icons"). If omitted, the default icon set of the environment is used. |

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": "search_icons",
    "arguments": {
      "tags": []
    }
  }
}
```

## Why search_icons is rated Low

This tool retrieves icon data based on keyword matching. It performs a read-only lookup of pre-existing Material Design icons without modifying, executing, or deleting anything. The worst-case misuse would be returning irrelevant icons, which has minimal blast radius. No financial, destructive, or code execution risks present.

From the tool's own definition: "Tool name is 'search_icons' and description states it 'Finds appropriate Material Design icons matching keywords' — a pure query/search operation with no side effects."

## Use case

AI agents call search_icons to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_icons": {}
  }
}
```

## Other tools on Mcp (4)

- `generate_color_scheme` — Execute — https://policylayer.com/tools/com-googleapis-design-mcp/generate-color-scheme.md
- `describe_font` — Read — https://policylayer.com/tools/com-googleapis-design-mcp/describe-font.md
- `icons_instructions` — Read — https://policylayer.com/tools/com-googleapis-design-mcp/icons-instructions.md
- `search_fonts` — Read — https://policylayer.com/tools/com-googleapis-design-mcp/search-fonts.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=com-googleapis-design-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-googleapis-design-mcp