Generate SSRF (Server-Side Request Forgery) test payloads for bug bounty testing. Creates unique identifiable URLs that can be injected into targets to detect blind SSRF vulnerabilities.
AI agents invoke generate_ssrf_payload to trigger actions in Webhook Site MCP Server. 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 generates attack payloads intended to be injected into target systems to trigger server-side requests. While it creates URLs/payloads (a Write-like action), its primary purpose is to facilitate SSRF exploitation against external targets, which constitutes an offensive security operation with significant external side effects.
From the tool's definition Generate SSRF (Server-Side Request Forgery) test payloads...injected into targets to detect blind SSRF vulnerabilities
Documented attack patterns abuse exactly the kind of access generate_ssrf_payload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Webhook Site MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_ssrf_payload:
{
"version": "1",
"default": "deny",
"tools": {
"generate_ssrf_payload": {
"limits": [
{
"counter": "generate_ssrf_payload_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}generate_ssrf_payload 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.
Generate SSRF (Server-Side Request Forgery) test payloads for bug bounty testing. Creates unique identifiable URLs that can be injected into targets to detect blind SSRF vulnerabilities. It is categorised as a Execute tool in the Webhook Site MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Webhook Site MCP Server MCP server in PolicyLayer and add a rule for generate_ssrf_payload: 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 Webhook Site MCP Server. Nothing to install.
generate_ssrf_payload 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 generate_ssrf_payload 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 generate_ssrf_payload. 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.
generate_ssrf_payload is provided by the Webhook Site MCP Server MCP server (zebbern/webhook-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Webhook Site MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Webhook Site MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.