Add travel insurance to protect the trip.
AI agents use travel_insurance to create or update resources in Flight Simulator MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flight Simulator MCP Server environment.
This tool creates or attaches a new service (travel insurance) to an existing booking, which is a write operation—it creates data and modifies the booking state. While it has financial implications (the customer will be charged for insurance), the primary action is a Write operation that creates/adds an insurance record.
From the tool's definition Tool name 'travel_insurance' and description 'Add travel insurance to protect the trip' indicate this creates or modifies a new insurance product addition to a booking.
Attacks that exploit this kind of access
Add travel insurance to protect the trip. It is categorised as a Write tool in the Flight Simulator MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Flight Simulator MCP Server MCP server in PolicyLayer and add a rule for travel_insurance: 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 Flight Simulator MCP Server. Nothing to install.
travel_insurance is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the travel_insurance 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 travel_insurance. 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.
travel_insurance is provided by the Flight Simulator MCP Server MCP server (jabir366/mcpfligh). 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 →