run_sql

Run one guarded, read-only PostgreSQL SELECT.

SERVERzoraHoldersAI SOURCEmarblerace/zoraHoldersAI

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/zoraholdersai/run-sql.md

WHAT IT DOES

What run_sql does on zoraHoldersAI

AI agents invoke run_sql to trigger actions in zoraHoldersAI. 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.

RISK

Why run_sql is rated High

run_sql triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_sql safely

PolicyLayer is an MCP gateway: it sits between your AI agents and zoraHoldersAI, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_sql, this is the rule to start with:

run_sql Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_sql": {
      "limits": [
        {
          "counter": "run_sql_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect zoraHoldersAI, apply this rule, and every run_sql call is checked against it from then on.

FAQ

Questions about run_sql

What does the run_sql tool do? +

Run one guarded, read-only PostgreSQL SELECT. It is categorised as a Execute tool in the zoraHoldersAI MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_sql? +

Register the zoraHoldersAI 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 zoraHoldersAI. Nothing to install.

What risk level is run_sql? +

run_sql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_sql? +

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.

How do I block run_sql completely? +

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.

What MCP server provides run_sql? +

run_sql is provided by the zoraHoldersAI MCP server (marblerace/zoraHoldersAI). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on zoraHoldersAI, and thousands of servers like it.

This server

All 4 zoraHoldersAI tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →