build_dsql_query · Wazuh MCP Server MCP: Risk & Policy

WHAT IT DOES

What build_dsql_query does on Wazuh MCP Server

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

WHY IT NEEDS A POLICY

Why build_dsql_query needs a policy

The 'build_dsql_query' function constructs dynamic SQL queries, which is an Execute-category capability. Even if the tool itself only builds queries without direct execution, the dynamic nature of SQL construction combined with the Wazuh security context (where queries affect agent monitoring, logs, and configurations) means misuse could trigger unintended data operations.

From the tool's definition Tool name 'build_dsql_query' indicates dynamic SQL query construction. In the context of a Wazuh security platform integration, this constructs and likely executes queries against security data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

build_dsql_query Rate-limited

build_dsql_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": {
    "build_dsql_query": {
      "limits": [
        {
          "counter": "build_dsql_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 Wazuh MCP Server, so you can run agents against it safely.

FAQ

Questions about build_dsql_query

What does the build_dsql_query tool do? +

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

How do I enforce a policy on build_dsql_query? +

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

What risk level is build_dsql_query? +

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

Can I rate-limit build_dsql_query? +

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

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

build_dsql_query is provided by the Wazuh MCP Server MCP server (rayasatriatama/wazuh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.