rpcclient_enumeration
A execute tool on the Nyxstrike MCP server.
This record as markdown: /tools/nyxstrike/rpcclient-enumeration.md
What rpcclient_enumeration does on Nyxstrike
AI agents invoke rpcclient_enumeration 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.
Why rpcclient_enumeration is rated High
rpcclient is a Unix/Linux tool used to execute RPC calls against Windows/Samba systems, commonly used for enumeration of users, shares, and domain information. On an offensive security platform alongside tools like aircrack-ng and payload generators, this tool likely executes rpcclient commands against target hosts.
From the tool's definition Tool name 'rpcclient_enumeration' on a penetration testing platform; description is empty but name implies running rpcclient for RPC/SMB enumeration against target systems
Attacks that exploit this kind of access
The rule that runs rpcclient_enumeration 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 rpcclient_enumeration, this is the rule to start with:
rpcclient_enumeration 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nyxstrike, apply this rule, and every rpcclient_enumeration call is checked against it from then on.
Questions about rpcclient_enumeration
rpcclient_enumeration 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.
Register the Nyxstrike MCP server in PolicyLayer and add a rule for rpcclient_enumeration: 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.
rpcclient_enumeration 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 rpcclient_enumeration 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 rpcclient_enumeration. 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.
rpcclient_enumeration 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.
More on Nyxstrike, and thousands of servers like it.
Across the catalogue