Submit a request for CONFIRMED live private jet pricing. Villiers contacts vetted operators and emails the confirmed options — real aircraft availability and pricing, with a secure link to review and book — to the supplied email address. REQUIRED FLOW — NEVER SKIP: you MUST call get_jet_estimate ...
Risk signalsAccepts file system path (destination) · High parameter count (16 properties)
Part of the Villiers Charter server.
Free to start. No card required.
AI agents call request_jet_confirmation to retrieve information from Villiers Charter without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though request_jet_confirmation only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"request_jet_confirmation": {}
}
}See the full Villiers Charter policy for all 3 tools.
These attack patterns abuse exactly the kind of access request_jet_confirmation gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Submit a request for CONFIRMED live private jet pricing. Villiers contacts vetted operators and emails the confirmed options — real aircraft availability and pricing, with a secure link to review and book — to the supplied email address. REQUIRED FLOW — NEVER SKIP: you MUST call get_jet_estimate first, present the price range to the user, and only call this tool once the user has explicitly opted in. Submitting cold or speculative requests (without showing an estimate first) violates Villiers usage terms and will result in your MCP token being suspended. Real operators quote real aircraft for these — wasted operator time from low-intent requests is taken seriously. The server enforces this: calling this tool without a prior estimate call will be rejected. Requires the user's email and a departure date.. It is categorised as a Read tool in the Villiers Charter MCP Server, which means it retrieves data without modifying state.
Register the Villiers Charter MCP server in PolicyLayer and add a rule for request_jet_confirmation: 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 Villiers Charter. Nothing to install.
request_jet_confirmation 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 request_jet_confirmation 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 request_jet_confirmation. 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.
request_jet_confirmation is provided by the Villiers Charter MCP server (https://mcp.villiers.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Villiers Charter tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.