Execute a SQL query against the financial database (SELECT only for security)
AI agents invoke run_sql to trigger actions in Quicken MCP Server. 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.
While the tool claims SELECT-only restriction, it is fundamentally an SQL execution tool operating on sensitive financial data (transactions, accounts, summaries from Quicken files). The security model depends on application-level filtering rather than database-level permissions or query whitelisting.
From the tool's definition Tool description states 'Execute a SQL query' - this is an Execute pattern. The '(SELECT only for security)' note indicates restriction to read-only operations, which would normally lower category to Read.
Documented attack patterns abuse exactly the kind of access run_sql gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Quicken MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_sql:
{
"version": "1",
"default": "deny",
"tools": {
"run_sql": {
"limits": [
{
"counter": "run_sql_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_sql 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.
Execute a SQL query against the financial database (SELECT only for security). It is categorised as a Execute tool in the Quicken MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Quicken MCP Server MCP server in PolicyLayer and add a rule for run_sql: 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 Quicken MCP Server. Nothing to install.
run_sql 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 run_sql 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 run_sql. 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.
run_sql is provided by the Quicken MCP Server MCP server (sgoley/quicken-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Quicken MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Quicken MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.