Update the airports database from the configured CSV source.
AI agents use update_airports_database to create or update resources in Flight Planner MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flight Planner MCP Server environment.
This tool modifies data (the airports database) in a reversible manner by updating it from a CSV source. It is not destructive because updates can typically be reverted by re-running with different source data. It does not delete data irreversibly, execute arbitrary code, or involve financial transactions.
From the tool's definition Tool name 'update_airports_database' and description state it 'Update the airports database from the configured CSV source.' The verb 'update' indicates modification of existing data.
Documented attack patterns abuse exactly the kind of access update_airports_database gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Flight Planner MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_airports_database:
{
"version": "1",
"default": "deny",
"tools": {
"update_airports_database": {
"limits": [
{
"counter": "update_airports_database_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_airports_database stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update the airports database from the configured CSV source. It is categorised as a Write tool in the Flight Planner MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Flight Planner MCP Server MCP server in PolicyLayer and add a rule for update_airports_database: 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 Planner MCP Server. Nothing to install.
update_airports_database 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 update_airports_database 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 update_airports_database. 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.
update_airports_database is provided by the Flight Planner MCP Server MCP server (salamentic/google-flights-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Flight Planner MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Flight Planner MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.