db_lookup_by_registration
AI agents call db_lookup_by_registration to retrieve information from Skyfly MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a lookup query against aviation data based on aircraft registration. Lookups are retrieval operations with no side effects—they query existing data without modification, creation, or deletion. The low severity reflects minimal blast radius: misuse would expose publicly available or semi-public aircraft information, not cause financial harm, data destruction, or code execution.
From the tool's definition Tool name 'db_lookup_by_registration' indicates a database lookup operation. The sibling tools (db_get_engine_info, db_get_model_info, db_get_reference_codes, db_get_stats, db_lookup_by_mode_s, db_search_aircraft, db_search_models) are all read-only query…
Attacks that exploit this kind of access
db_lookup_by_registration. It is categorised as a Read tool in the Skyfly MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Skyfly MCP Server MCP server in PolicyLayer and add a rule for db_lookup_by_registration: 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 Skyfly MCP Server. Nothing to install.
db_lookup_by_registration 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 db_lookup_by_registration 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 db_lookup_by_registration. 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.
db_lookup_by_registration is provided by the Skyfly MCP Server MCP server (vog01r/skyfly-mcp). 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 →