db_get_engine_info
AI agents call db_get_engine_info 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 appears designed to fetch aircraft engine specifications from the aviation database. The naming convention and server context indicate a read-only retrieval operation. Without a description, confidence is moderately lowered, but the consistent naming pattern of sibling read tools supports the Read classification.
From the tool's definition Tool name 'db_get_engine_info' indicates a retrieval operation ('get'); sibling tools on the same server show a consistent pattern of read operations (db_get_model_info, db_get_reference_codes, db_get_stats, db_lookup_by_mode_s, db_lookup_by_registration,…
Attacks that exploit this kind of access
db_get_engine_info. 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_get_engine_info: 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_get_engine_info 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_get_engine_info 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_get_engine_info. 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_get_engine_info 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 →