Performs security testing on web applications via HTTP/HTTPS. Supports external URLs with authorization. Tests security headers, SSL/TLS, information disclosure, cookies, CORS, and more.
AI agents invoke pentest_website to trigger actions in MCP Shamash. 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/penetration tests against web applications, sending crafted HTTP requests to probe for vulnerabilities. It is not merely reading data — it performs active operations against external targets.
From the tool's definition 'Performs security testing on web applications via HTTP/HTTPS' and 'Tests security headers, SSL/TLS, information disclosure, cookies, CORS, and more' — actively sends HTTP requests and probes to external targets
Attacks that exploit this kind of access
Performs security testing on web applications via HTTP/HTTPS. Supports external URLs with authorization. Tests security headers, SSL/TLS, information disclosure, cookies, CORS, and more. It is categorised as a Execute tool in the MCP Shamash MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Shamash MCP server in PolicyLayer and add a rule for pentest_website: 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 MCP Shamash. Nothing to install.
pentest_website 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 pentest_website 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 pentest_website. 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.
pentest_website is provided by the MCP Shamash MCP server (neotecdigital/mcp_shamash). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →