# tower_detail

Full data for an antenna structure by ASR registration number — owner, location, height, declared licensees on the tower, microwave paths terminating there, and licensees within 50 m by spatial proximity. Returns Markdown.

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

## Facts

- Tool: `tower_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 |
| --- | --- | --- | --- |
| `asr_number` | integer | yes | 7-digit ASR registration number |

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": "tower_detail",
    "arguments": {
      "asr_number": 0
    }
  }
}
```

## Why tower_detail is rated Low

This is a read-only data retrieval tool that queries FCC database records about antenna tower structures and related license information. It has no side effects, makes no modifications, executes no code, and poses minimal risk even if misused by an AI agent—it only surfaces publicly-available FCC regulatory data.

From the tool's own definition: "Tool retrieves and returns full data about antenna structures (owner, location, height, licensees, microwave paths) by ASR registration number."

## Use case

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

## Other tools on Fccdb (3)

- `license_detail` — Read — https://policylayer.com/tools/com-fccdb-api/license-detail.md
- `path_profile` — Read — https://policylayer.com/tools/com-fccdb-api/path-profile.md
- `search` — Read — https://policylayer.com/tools/com-fccdb-api/search.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