test_privesc
Run privilege escalation enumeration on a compromised host. Platforms: linux, windows, container. Uses linpeas/winpeas/deepce plus kernel-exploit-suggester. Enumeration only by default. Returns immediately with engagement_id; agent runs asynchronously.
This record as markdown: /tools/0xsteph-pentest-ai/test-privesc.md
What test_privesc does on Pentest Ai
AI agents invoke test_privesc to trigger actions in Pentest Ai. 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 test_privesc is rated High
This tool actively executes security enumeration tools (linpeas, winpeas, deepce, kernel-exploit-suggester) on a compromised host to identify privilege escalation paths. While described as 'enumeration only by default,' it runs real offensive security tools on live systems, which is an Execute-category action with critical severity — misuse could expose full privilege escalation paths on production systems,…
From the tool's definition 'Run privilege escalation enumeration on a compromised host' using 'linpeas/winpeas/deepce plus kernel-exploit-suggester' on 'linux, windows, container' platforms
Attacks that exploit this kind of access
The rule that runs test_privesc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pentest Ai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test_privesc, this is the rule to start with:
test_privesc 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 Pentest Ai, apply this rule, and every test_privesc call is checked against it from then on.
Questions about test_privesc
Run privilege escalation enumeration on a compromised host. Platforms: linux, windows, container. Uses linpeas/winpeas/deepce plus kernel-exploit-suggester. Enumeration only by default. Returns immediately with engagement_id; agent runs asynchronously. It is categorised as a Execute tool in the Pentest Ai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pentest Ai MCP server in PolicyLayer and add a rule for test_privesc: 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 Pentest Ai. Nothing to install.
test_privesc 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 test_privesc 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 test_privesc. 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.
test_privesc is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pentest Ai, and thousands of servers like it.
Across the catalogue