Executes a SQL query in the Firebird database. Uses FIRST/ROWS for pagination.
AI agents invoke execute-query to trigger actions in Mcp Firebird. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
sql | string | Yes | SQL query to execute (Firebird uses FIRST/ROWS for pagination instead of LIMIT) |
params | array | — | Parameters for parameterized queries to prevent SQL injection |
Parameters from the server's own tool schema.
SQL query execution is inherently an Execute category risk because effects are argument-dependent and can range from benign reads to destructive modifications. The sibling tool 'execute-batch-queries' reinforces that multiple arbitrary queries can be run.
From the tool's definition Tool explicitly 'Executes a SQL query' in a database without specifying read-only constraints. Combined with sibling tools including 'execute-batch-queries' and the absence of any qualifier like 'select-only' or 'read-only', this enables arbitrary SQL…
Risk signalsAccepts freeform code/query input (sql)
Attacks that exploit this kind of access
Executes a SQL query in the Firebird database. Uses FIRST/ROWS for pagination. It is categorised as a Execute tool in the Mcp Firebird MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
execute-query 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 execute-query: 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.
execute-query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute-query 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 execute-query. 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.
execute-query 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 →