cme_mssql · CrackMapExec MCP Server MCP: Risk & Policy

WHAT IT DOES

What cme_mssql does on CrackMapExec MCP Server

AI agents invoke cme_mssql to trigger actions in CrackMapExec 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 cme_mssql needs a policy

This tool enables arbitrary code execution through two vectors: (1) SQL query execution against MSSQL databases, which can modify data, escalate privileges, or trigger stored procedures; (2) direct command execution via xp_cmdshell, which runs OS-level commands with the privileges of the SQL Server service account.

From the tool's definition Tool supports "SQL query execution and command execution via xp_cmdshell" - these are operations that execute arbitrary code with effects determined by the provided arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cme_mssql Rate-limited

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

FAQ

Questions about cme_mssql

What does the cme_mssql tool do? +

Execute MSSQL protocol operations. Supports SQL query execution and command execution via xp_cmdshell. It is categorised as a Execute tool in the CrackMapExec 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 cme_mssql? +

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

What risk level is cme_mssql? +

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

Can I rate-limit cme_mssql? +

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

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

cme_mssql is provided by the CrackMapExec MCP Server MCP server (schwarztim/sec-crackmapexec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.