Create a new webhook.site endpoint with custom configuration (response content, status, timeout, CORS, alias).
AI agents use create_webhook_with_config to create or update resources in Webhook Site MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Webhook Site MCP Server environment.
This tool creates a new webhook endpoint, which is a reversible data/resource creation operation. It falls under Write category rather than Execute because it does not run arbitrary code or commands—it simply provisions a new endpoint with predefined configuration options.
From the tool's definition Tool name 'create_webhook' and description 'Create a new webhook.site endpoint' directly indicates creation of a new resource.
Documented attack patterns abuse exactly the kind of access create_webhook_with_config 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 create_webhook_with_config:
{
"version": "1",
"default": "deny",
"tools": {
"create_webhook_with_config": {
"limits": [
{
"counter": "create_webhook_with_config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_webhook_with_config stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new webhook.site endpoint with custom configuration (response content, status, timeout, CORS, alias). It is categorised as a Write tool in the Webhook Site MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Webhook Site MCP Server MCP server in PolicyLayer and add a rule for create_webhook_with_config: 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.
create_webhook_with_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_webhook_with_config 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 create_webhook_with_config. 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.
create_webhook_with_config 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.