3 tools. 2 can modify or destroy data without limits.
2 destructive tools with no built-in limits. Policy required.
Last updated:
Financial operations (book_london_airport_transfer, london_airport_transfer_quote) can move real money. An agent caught in a loop could drain accounts before anyone notices.
Intercept sits between your agent and London Airport Transfers. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @airport-pickups-london/London-airport-transfers book_london_airport_transfer:
rules:
- action: deny Financial tools should be explicitly enabled per use case, not open by default.
validate_flight:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The London Airport Transfers server exposes 2 financial tools including book_london_airport_transfer, london_airport_transfer_quote. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. Intercept lets you block financial tools by default or set per-tool rate limits.
3 tools across 2 categories: Financial, Read. 1 are read-only. 2 can modify, create, or delete data.
One line change. Instead of running the London Airport Transfers server directly, prefix it with Intercept: intercept -c airport-pickups-london-london-airport-transfers.yaml -- npx -y @airport-pickups-london/London-airport-transfers. Download a pre-built policy from policylayer.com/policies/airport-pickups-london-london-airport-transfers and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init