Batch lookup of aircraft details by ICAO24 hex codes (max 20). Returns registration, type, operator from hexdb.io.
AI agents call intel_aircraft_batch to retrieve information from Threat Intelligence MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a public aircraft database (hexdb.io) to retrieve static aircraft information. It performs a read-only lookup operation with no side effects, data modification, code execution, or financial impact. The maximum batch size of 20 lookups is a reasonable limit.
From the tool's definition Tool description explicitly states 'Batch lookup of aircraft details' and 'Returns registration, type, operator' — pure retrieval of public aircraft data with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access intel_aircraft_batch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Threat Intelligence MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for intel_aircraft_batch:
{
"version": "1",
"default": "deny",
"tools": {
"intel_aircraft_batch": {}
}
}intel_aircraft_batch is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Batch lookup of aircraft details by ICAO24 hex codes (max 20). Returns registration, type, operator from hexdb.io. It is categorised as a Read tool in the Threat Intelligence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Threat Intelligence MCP Server MCP server in PolicyLayer and add a rule for intel_aircraft_batch: 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 Threat Intelligence MCP Server. Nothing to install.
intel_aircraft_batch 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 intel_aircraft_batch 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 intel_aircraft_batch. 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.
intel_aircraft_batch is provided by the Threat Intelligence MCP Server MCP server (marc-shade/world-intel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Threat Intelligence MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
113 Threat Intelligence MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.