# path_profile

Metadata for a single microwave path on a license. Identified by the ULS USI (per-license integer) and the path number within that license. The HTML page has an SVG elevation chart with terrain + line of sight + Fresnel zone; the Markdown response carries the endpoints, length, and frequency but not the chart.

Agent View of the PolicyLayer registry record for `path_profile`. HTML page: https://policylayer.com/tools/com-fccdb-api/path-profile

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `usi` | integer | yes | ULS USI (license id) |
| `path_number` | integer | yes | Path number within the license |

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": "path_profile",
    "arguments": {
      "usi": 0,
      "path_number": 0
    }
  }
}
```

## Why path_profile is rated Low

This tool queries and returns data about FCC microwave paths without any side effects. It accepts identifiers (ULS USI and path number) as arguments and returns metadata and visualization—classic Read category behavior. No data is created, modified, deleted, or executed; it is a pure retrieval operation. Severity is low because unauthorized access to publicly available FCC license information carries minimal risk.

From the tool's own definition: "Tool retrieves 'Metadata for a single microwave path on a license' including 'endpoints, length, and frequency' with visualization via SVG chart. Operations are purely informational queries with no modification, deletion, or execution capability."

## Use case

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

## Other tools on Fccdb (3)

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