Dynamic escalation scores for 22 intel hotspots combining news, military, conflict, and convergence signals. Each hotspot scored 0-100.
AI agents call intel_hotspot_escalation 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.
The tool retrieves and presents calculated intelligence scores about geopolitical hotspots. It has no side effects, does not execute commands, does not modify data, and does not move money. It functions as an informational read-only service that queries and synthesizes existing intelligence sources to produce risk assessment metrics. The 'dynamic escalation scores' are outputs of analysis, not triggers for actions.
From the tool's definition Tool provides 'escalation scores' for intelligence hotspots by 'combining news, military, conflict, and convergence signals.' This is purely a data retrieval and scoring operation that reads and aggregates existing threat intelligence data.
Documented attack patterns abuse exactly the kind of access intel_hotspot_escalation 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_hotspot_escalation:
{
"version": "1",
"default": "deny",
"tools": {
"intel_hotspot_escalation": {}
}
}intel_hotspot_escalation 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.
Dynamic escalation scores for 22 intel hotspots combining news, military, conflict, and convergence signals. Each hotspot scored 0-100. 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_hotspot_escalation: 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_hotspot_escalation 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_hotspot_escalation 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_hotspot_escalation. 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_hotspot_escalation 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.