query_trace_sql

Execute a read-only SQL query against a trace database.

SERVERJshookmcp SOURCE@jshookmcp/jshook

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/query-trace-sql.md

WHAT IT DOES

What query_trace_sql does on Jshookmcp

AI agents invoke query_trace_sql to trigger actions in Jshookmcp. 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 query_trace_sql is rated High

Runs SQL queries against a database; read-only but executes code with potential for large data exposure.

From the tool's definition Execute a read-only SQL query against a trace database

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_trace_sql safely

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

query_trace_sql Rate-limited

query_trace_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": {
    "query_trace_sql": {
      "limits": [
        {
          "counter": "query_trace_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 Jshookmcp, apply this rule, and every query_trace_sql call is checked against it from then on.

FAQ

Questions about query_trace_sql

What does the query_trace_sql tool do? +

Execute a read-only SQL query against a trace database. It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on query_trace_sql? +

Register the Jshook MCP server in PolicyLayer and add a rule for query_trace_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 Jshookmcp. Nothing to install.

What risk level is query_trace_sql? +

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

Can I rate-limit query_trace_sql? +

Yes. Add a rate_limit block to the query_trace_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 query_trace_sql completely? +

Set action: deny in the PolicyLayer policy for query_trace_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 query_trace_sql? +

query_trace_sql is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools → High-risk tools on this server →

Across the catalogue

aroflo_query_zone on AroFlo MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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