Run built-in security scans without requiring any external tools. Works immediately after install. Scan types: all, ports, headers, ssl, paths, dns, secrets. Includes: port scanning, HTTP header analysis, SSL/TLS checks, sensitive path discovery, DNS enumeration, and secret/credential detection i...
AI agents invoke builtin_scan 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.
This tool actively executes security scanning operations against external targets — including port scanning, DNS enumeration, and sensitive path discovery. These are active network operations with real-world effects on target systems (triggering IDS alerts, consuming target resources, potentially constituting unauthorized access). It doesn't merely read local data; it initiates outbound probes.
From the tool's definition "Run built-in security scans", "port scanning, HTTP header analysis, SSL/TLS checks, sensitive path discovery, DNS enumeration, and secret/credential detection in responses"
Documented attack patterns abuse exactly the kind of access builtin_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentest Ai, and nothing reaches the server without passing your rules. This is the rule we recommend for builtin_scan:
{
"version": "1",
"default": "deny",
"tools": {
"builtin_scan": {
"limits": [
{
"counter": "builtin_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}builtin_scan 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.
Free to start. No card required.
Run built-in security scans without requiring any external tools. Works immediately after install. Scan types: all, ports, headers, ssl, paths, dns, secrets. Includes: port scanning, HTTP header analysis, SSL/TLS checks, sensitive path discovery, DNS enumeration, and secret/credential detection in responses. 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 builtin_scan: 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.
builtin_scan 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 builtin_scan 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 builtin_scan. 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.
builtin_scan 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.
Deterministic rules across all 51 Pentest Ai tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
51 Pentest Ai tools catalogued and risk-classified — across an index of 42,500+ MCP servers.