TSA daily passenger volumes — throughput data from US airport checkpoints. WHEN TO USE: To track airport passenger volumes and compare to historical levels. Useful for travel industry analysis and consumer spending indicators. RETURNS: Daily passenger counts, year-over-year comparison, and trend ...
AI agents call veroq_travel_tsa 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 is a data retrieval tool that queries publicly-available or aggregated TSA passenger volume statistics. It has no capability to modify, delete, or execute operations—it simply fetches historical and comparative traffic data for analysis. The use case is explicitly analytical ('travel industry analysis and consumer spending indicators').
From the tool's definition Retrieves 'daily passenger counts, year-over-year comparison, and trend data' from TSA checkpoints with no modification capability. Tool name and description indicate data retrieval only: 'To track airport passenger volumes' (passive observation).
Attacks that exploit this kind of access
TSA daily passenger volumes — throughput data from US airport checkpoints. WHEN TO USE: To track airport passenger volumes and compare to historical levels. Useful for travel industry analysis and consumer spending indicators. RETURNS: Daily passenger counts, year-over-year comparison, and trend data. 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_tsa: 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_tsa 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_tsa 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_tsa. 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_tsa 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 →