run_custom_query · Mcp Strategy Research Db MCP

WHAT IT DOES

What run_custom_query does on Mcp Strategy Research Db

AI agents invoke run_custom_query to trigger actions in Mcp Strategy Research Db. 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.

WHY IT NEEDS A POLICY

Why run_custom_query needs a policy

This tool allows execution of user-supplied SQL queries with minimal constraints. While the description restricts to SELECT and PRAGMA (read-only), custom query execution tools are inherently dangerous because: (1) SQL query execution is a form of code execution, (2) query constraints may be bypassable or incompletely enforced, (3) even SELECT queries can be weaponized for exfiltration or denial of service…

From the tool's definition Tool name 'run_custom_query' and description states it will 'Execute a custom SQL query' against the database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_custom_query Rate-limited

run_custom_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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Strategy Research Db, so you can run agents against it safely.

FAQ

Questions about run_custom_query

What does the run_custom_query tool do? +

Execute a custom SQL query against the strategy database. For advanced users who need specific analysis not covered by other tools. Supports SELECT queries and PRAGMA commands for schema inspection. It is categorised as a Execute tool in the Mcp Strategy Research Db 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_custom_query? +

Register the Mcp Strategy Research Db MCP server in PolicyLayer and add a rule for run_custom_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 Strategy Research Db. Nothing to install.

What risk level is run_custom_query? +

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

Can I rate-limit run_custom_query? +

Yes. Add a rate_limit block to the run_custom_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.

How do I block run_custom_query completely? +

Set action: deny in the PolicyLayer policy for run_custom_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.

What MCP server provides run_custom_query? +

run_custom_query is provided by the Mcp Strategy Research Db MCP server (locupleto/mcp-strategy-research-db). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.