license_detail
Full data for a single FCC license by call sign — licensee, locations with coordinates, antennas, paths, frequencies. Returns Markdown.
This record as markdown: /tools/com-fccdb-api/license-detail.md
What license_detail does on Fccdb
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
call_sign | string | Yes | FCC call sign, e.g. KAC75 |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs license_detail 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 license_detail, this is the rule to start with:
license_detail 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 license_detail call is checked against it from then on.
Questions about license_detail
Full data for a single FCC license by call sign — licensee, locations with coordinates, antennas, paths, frequencies. Returns Markdown. It is categorised as a Read tool in the Fccdb MCP Server, which means it retrieves data without modifying state.
license_detail accepts 1 parameter: call_sign. Required: call_sign. 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 license_detail: 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.
license_detail 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 license_detail 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 license_detail. 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.
license_detail 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