Gets the execution plan for a SQL query to understand how the database will execute it
AI agents call get-execution-plan to retrieve information from MCP Firebird without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays the execution plan (query optimization metadata) from the database. It does not execute the actual query against data, nor does it modify, delete, or create any data. It is purely informational, similar to EXPLAIN PLAN operations in SQL databases.
From the tool's definition Tool name 'get-execution-plan' and description 'Gets the execution plan for a SQL query to understand how the database will execute it' indicate retrieval and analysis of query metadata without executing the query itself or modifying data.
Attacks that exploit this kind of access
Gets the execution plan for a SQL query to understand how the database will execute it. It is categorised as a Read tool in the MCP Firebird MCP Server, which means it retrieves data without modifying state.
Register the MCP Firebird MCP server in PolicyLayer and add a rule for get-execution-plan: 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 MCP Firebird. Nothing to install.
get-execution-plan 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 get-execution-plan 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 get-execution-plan. 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.
get-execution-plan is provided by the MCP Firebird MCP server (luancamara/mcpfirebird). 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 →