Execute NetExec MSSQL protocol commands for SQL Server enumeration and command execution.
AI agents invoke nxc_mssql to trigger actions in Sec Netexec. 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.
This tool enables execution of arbitrary commands against SQL Server instances via the MSSQL protocol. Even if framed as 'enumeration,' the explicit mention of 'command execution' means an AI agent could run malicious SQL commands, extract sensitive data, modify database contents, or pivot to other systems.
From the tool's definition Tool description states 'Execute NetExec MSSQL protocol commands for SQL Server enumeration and command execution.' The word 'Execute' directly indicates code/command execution capability.
Attacks that exploit this kind of access
Execute NetExec MSSQL protocol commands for SQL Server enumeration and command execution. It is categorised as a Execute tool in the Sec Netexec MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sec Netexec MCP server in PolicyLayer and add a rule for nxc_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 Sec Netexec. Nothing to install.
nxc_mssql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the nxc_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.
Set action: deny in the PolicyLayer policy for nxc_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.
nxc_mssql is provided by the Sec Netexec MCP server (schwarztim/sec-netexec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →