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.
| Parameter | Type | Required | Description |
|---|---|---|---|
sql | string | Yes | SQL query to analyze |
params | array | — | Parameters for parameterized queries |
Parameters from the server's own tool schema.
This tool retrieves and displays database query execution plans—informational output about how a query will be processed. It does not create, modify, or delete data; does not execute the actual query; and does not trigger external operations. It is a pure read operation that returns analytical metadata about query execution strategy.
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 a query analysis operation that retrieves execution metadata without modifying data or executing the query itself.
Risk signalsAccepts freeform code/query input (sql)
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.
get-execution-plan accepts 2 parameters: sql, params. Required: sql. The full parameter table on this page comes from the server's own tool schema.
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 (mcp-firebird). 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 →