# describe_font

Describes a font family in detail, including its look and feel, supported styles, weights and how to use it.

Agent View of the PolicyLayer registry record for `describe_font`. HTML page: https://policylayer.com/tools/com-googleapis-design-mcp/describe-font

## Facts

- Tool: `describe_font`
- 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 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `platform` | string | yes | Required. The platform in which the font family is going to be used. |
| `fontFamily` | string | yes | Required. The full name of the font family to describe. Example: "Roboto", "Noto Sans". |

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": "describe_font",
    "arguments": {
      "platform": "<platform>",
      "fontFamily": "<fontFamily>"
    }
  }
}
```

## Why describe_font is rated Low

Even though describe_font only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call describe_font 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": {
    "describe_font": {}
  }
}
```

## Other tools on Mcp (4)

- `generate_color_scheme` — Execute — https://policylayer.com/tools/com-googleapis-design-mcp/generate-color-scheme.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
- `search_icons` — Read — https://policylayer.com/tools/com-googleapis-design-mcp/search-icons.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