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.
This tool allows execution of arbitrary SQL queries against a live database. While the description does not explicitly mention DELETE, DROP, or destructive operations, SQL query execution inherently permits such operations depending on query arguments. The tool's effects are entirely argument-dependent (the SQL provided).
From the tool's definition Tool explicitly 'Executes a SQL query in the Firebird database'. The name 'execute-query' and description confirm arbitrary SQL execution capability.
Documented attack patterns abuse exactly the kind of access execute-query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Firebird, and nothing reaches the server without passing your rules. This is the rule we recommend for execute-query:
{
"version": "1",
"default": "deny",
"tools": {
"execute-query": {
"limits": [
{
"counter": "execute-query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute-query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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 (purodelphi/mcpfirebird). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 MCP Firebird tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 MCP Firebird tools catalogued and risk-classified — across an index of 42,500+ MCP servers.