add_services
AI agents use add_services 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.
The tool most likely creates or modifies booking records by appending services, which is a Write action. Severity is medium because misuse could incur unexpected charges or service additions, but changes are reversible through cancellation/modification.
From the tool's definition Tool name 'add_services' combined with server context (airline booking operations). No explicit description provided, but the name and server purpose suggest adding optional services (luggage, seat upgrades, meals, etc.) to bookings—a reversible modification…
Attacks that exploit this kind of access
add_services. 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 add_services: 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.
add_services 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 add_services 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 add_services. 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.
add_services 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 →