PenterDocumentationTools & runtime extensions
Documentation

Tools & runtime extensions

Learn about the tools available during public beta, including scoped Browser/HTTP and optional offline Docker. Shell, WSL and MCP execution are not yet available.

Packaged public beta execution restrictions
Native shell, WSL/Kali subprocesses, MCP processes and networked Docker execution are blocked in the packaged beta. Managed Docker supports offline network=none only. Use scoped Browser/HTTP/Request Lab tools for authorized target work; documentation below also describes capabilities that are not yet enabled in the public build.
01

Tool categories

CategoryExamplesExecution boundary
Built-in desktop toolsHTTP requests, Browser Agent, code grep; native shell currently blocked in packaged beta.Desktop runtime with beta restrictions.
Kali knowledgetools.search, tools.help.Read installed command names/help from the desktop/WSL environment.
Custom executable toolsSaved command templates with named placeholders.Rendered into a normal shell.command path.
MCPmcp.listServers, mcp.listTools, mcp.call.Connected stdio child process in Electron main.
Cloud executionDisabled during the public beta; this is separate from Cloud AI chat.Unavailable until release approval.
Specialist delegationrecon, web, auth, injection, verification.Isolated model analysis; no direct execution bypass.
02

Kali tools and WSL availability

PENTER does not inject thousands of tool manuals into every prompt. Agents can first search the installed command catalog, then read exact local help/man output for the command they actually intend to use.

Agent tool flow
tools.search({ query: "ldap" })
tools.help({ command: "ldapsearch" })
Why this matters
Tool syntax changes, distributions differ and many security commands have complex flags. Grounding the agent in the locally installed help text reduces hallucinated options and avoids wasting context on unrelated tools.
03

Create custom executable tools

Open the Extensions/Plugins view and add a custom tool with a name, description, command template and optional tags. Placeholders use braces and become named arguments that the agent supplies through customTool.run.

Template
nuclei -u {url} -tags {tags}
Agent-side invocation
customTool.run
toolId: my-nuclei
arguments: { "url": "https://authorized.example", "tags": "exposure,misconfig" }
  • Missing placeholders cause the custom tool call to fail instead of silently rendering an incomplete command.
  • Newline and NUL characters are stripped from placeholder values before substitution.
  • Disabled custom tools disappear from the enabled tool list exposed to agents.
  • The final rendered command goes through the normal shell-command execution/approval path.
Templates are powerful
A placeholder is not a full shell sandbox. Only create templates you understand, keep them narrow, and review the rendered command at approval time.
04

Background-capable tool work

PENTER exposes a background-tool wrapper for selected non-shell actions. The current supported set includes HTTP request, Browser Agent action, code grep and web search aliases. This lets the conversation continue while a supported non-shell task is running.

Why shell scanners are different

Shell/scanner processes remain foreground in the current runtime path because robust per-process cancellation and lifecycle management is a different problem from backgrounding a bounded in-process/browser request.
05

Extensions do not bypass approval

Custom executable tools eventually become a shell command. MCP tool calls have their own explicit approval binding. Starting an MCP server is also approval-gated. This keeps the extension layer from becoming a side door around PENTER's normal operator-control model.

  • Review command/tool name and arguments before granting approval.
  • Prefer one narrow extension over a general-purpose wrapper when possible.
  • Keep extension credentials in the extension/MCP environment rather than embedding them in a command template.
  • Disable or remove extensions that are not needed for the active engagement.
Next step

Ready to get started?

Follow the setup guide, install the current approved Desktop release, and connect your account.