sqlite_query

A execute tool on the Nyxstrike MCP server.

SERVERNyxstrike SOURCECommonHuman-Lab/nyxstrike

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/nyxstrike/sqlite-query.md

WHAT IT DOES

What sqlite_query does on Nyxstrike

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

The tool name suggests arbitrary SQLite query execution. On an offensive security platform alongside tools like payload generation and vulnerability assessment, this likely allows running arbitrary SQL including destructive statements (DROP, DELETE). Empty description lowers confidence slightly, but the context and name strongly suggest Execute or Destructive capability.

From the tool's definition Tool name is 'sqlite_query' on a penetration testing platform; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sqlite_query safely

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

sqlite_query Rate-limited

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

FAQ

Questions about sqlite_query

What does the sqlite_query tool do? +

sqlite_query is a execute tool on the Nyxstrike MCP server. It is categorised as a Execute tool in the Nyxstrike MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sqlite_query? +

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

What risk level is sqlite_query? +

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

Can I rate-limit sqlite_query? +

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

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

sqlite_query is provided by the Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nyxstrike, and thousands of servers like it.

This server

All 221 Nyxstrike 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 →