Query 27+ launch facilities and spaceports worldwide. Filterable by country, status, type (orbital/suborbital), and operator.
AI agents call intel_spaceports 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 retrieves and filters public reference data about spaceports with no side effects. It is purely informational—querying a static or semi-static database of facility information. No data modification, code execution, or destructive operations are possible. The low severity reflects minimal risk even if misused by an agent, as the output is non-sensitive infrastructure reference data.
From the tool's definition Tool performs 'Query' operations on spaceport data with filtering parameters (country, status, type, operator).
Documented attack patterns abuse exactly the kind of access intel_spaceports 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_spaceports:
{
"version": "1",
"default": "deny",
"tools": {
"intel_spaceports": {}
}
}intel_spaceports 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.
Query 27+ launch facilities and spaceports worldwide. Filterable by country, status, type (orbital/suborbital), and operator. 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_spaceports: 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_spaceports 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_spaceports 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_spaceports. 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_spaceports 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.