scan_paths_builtin
Scan for common sensitive paths (built-in).
This record as markdown: /tools/0xsteph-pentest-ai/scan-paths-builtin.md
What scan_paths_builtin does on Pentest Ai
AI agents call scan_paths_builtin to retrieve information from Pentest Ai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why scan_paths_builtin is rated Low
This tool performs reconnaissance by scanning for sensitive paths, which is a read/discovery operation. It retrieves information about accessible paths without modifying or destroying data. However, in a pentesting context, discovering sensitive paths could expose credentials or configuration files, giving it medium severity if misused against unauthorized targets.
From the tool's definition Scan for common sensitive paths (built-in)
Attacks that exploit this kind of access
The rule that runs scan_paths_builtin 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 scan_paths_builtin, this is the rule to start with:
scan_paths_builtin is read-only, so it stays allowed. 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 scan_paths_builtin call is checked against it from then on.
Questions about scan_paths_builtin
Scan for common sensitive paths (built-in). It is categorised as a Read tool in the Pentest Ai MCP Server, which means it retrieves data without modifying state.
Register the Pentest Ai MCP server in PolicyLayer and add a rule for scan_paths_builtin: 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.
scan_paths_builtin is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the scan_paths_builtin 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 scan_paths_builtin. 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.
scan_paths_builtin 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.
This server
Across the catalogue