# license_detail

Full data for a single FCC license by call sign — licensee, locations with coordinates, antennas, paths, frequencies. Returns Markdown.

Agent View of the PolicyLayer registry record for `license_detail`. HTML page: https://policylayer.com/tools/com-fccdb-api/license-detail

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `call_sign` | string | yes | FCC call sign, e.g. KAC75 |

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": "license_detail",
    "arguments": {
      "call_sign": "<call_sign>"
    }
  }
}
```

## Why license_detail is rated Low

This tool retrieves and queries data from the FCC ULS (Universal Licensing System) database. It fetches license information, licensee details, locations, antennas, paths, and frequencies for a given call sign—all read-only operations. There is no modification, deletion, execution of code, or financial transaction involved. The data returned is public FCC regulatory information.

From the tool's own definition: "Tool name 'license_detail' and description 'Full data for a single FCC license' indicates retrieval of existing public FCC database records. The verb 'returns' and phrase 'by call sign' confirm query/fetch semantics with no side effects."

## Use case

AI agents call license_detail to retrieve information from Fccdb 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 Fccdb:

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

## Other tools on Fccdb (3)

- `path_profile` — Read — https://policylayer.com/tools/com-fccdb-api/path-profile.md
- `search` — Read — https://policylayer.com/tools/com-fccdb-api/search.md
- `tower_detail` — Read — https://policylayer.com/tools/com-fccdb-api/tower-detail.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-fccdb-api · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-fccdb-api