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 ...
This record as markdown: /tools/com-fccdb-api/path-profile.md
What path_profile does on Fccdb
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.
| 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.
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 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.
Attacks that exploit this kind of access
The rule that runs path_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fccdb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For path_profile, this is the rule to start with:
path_profile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Fccdb, apply this rule, and every path_profile call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Fccdb MCP Server, which means it retrieves data without modifying state.
path_profile accepts 2 parameters: usi, path_number. Required: usi, path_number. The full parameter table on this page comes from the server's own tool schema.
Register the Fccdb MCP server in PolicyLayer and add a rule for path_profile: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Fccdb. Nothing to install.
path_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the path_profile rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for path_profile. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
path_profile is provided by the Fccdb MCP server (https://fccdb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fccdb, and thousands of servers like it.
This server
Across the catalogue