Travel disruption score combining TSA volumes, FAA delays, and border wait times. WHEN TO USE: For a quick snapshot of US travel conditions — airport delays, passenger throughput, and border crossing waits. RETURNS: Composite disruption score, TSA passenger counts, FAA ground stops, and border wa...
AI agents call veroq_travel_overview to retrieve information from Veroq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only—it aggregates publicly available travel status information (TSA passenger volumes, FAA delays, border wait times) and returns a composite view. It has no side effects, does not modify data, execute commands, or trigger financial transactions. It is a pure Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool retrieves and queries travel data: 'TSA volumes, FAA delays, and border wait times' and 'returns composite disruption score, TSA passenger counts, FAA ground stops, and border wait times.' No modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Travel disruption score combining TSA volumes, FAA delays, and border wait times. WHEN TO USE: For a quick snapshot of US travel conditions — airport delays, passenger throughput, and border crossing waits. RETURNS: Composite disruption score, TSA passenger counts, FAA ground stops, and border wait times. COST: 1 credit. EXAMPLE: {}. It is categorised as a Read tool in the Veroq MCP Server, which means it retrieves data without modifying state.
Register the Veroq MCP server in PolicyLayer and add a rule for veroq_travel_overview: 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 Veroq. Nothing to install.
veroq_travel_overview 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 veroq_travel_overview 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 veroq_travel_overview. 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.
veroq_travel_overview is provided by the Veroq MCP server (veroq-ai/veroq-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →