Get complete trip history for a specific customer, including statistics like total trips, spending, and trip details ordered by date.
AI agents call get_trip_history to retrieve information from Travel Company MCP Server 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 operation that accesses customer trip records and spending statistics. It is classified as Read because it performs a query with no side effects.
From the tool's definition The tool 'get_trip_history' retrieves 'complete trip history for a specific customer, including statistics like total trips, spending, and trip details' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get complete trip history for a specific customer, including statistics like total trips, spending, and trip details ordered by date. It is categorised as a Read tool in the Travel Company MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Travel Company MCP Server MCP server in PolicyLayer and add a rule for get_trip_history: 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 Travel Company MCP Server. Nothing to install.
get_trip_history 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 get_trip_history 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 get_trip_history. 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.
get_trip_history is provided by the Travel Company MCP Server MCP server (stefanjwojcik/mcpdemo). 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 →