Provision an inbound webhook receiver URL on instanode.dev. Returns a receive_url that accepts any HTTP method from any sender and stores each request (method, headers, body, received_at). GET the same URL to pull back the stored log. The 'name' field is required. Useful for: testing Stripe/Git...
Part of the Instanode MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use create_webhook to create or modify resources in Instanode. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call create_webhook repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Instanode.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
create_webhook:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Instanode policy for all 6 tools.
Agents calling write-class tools like create_webhook have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Provision an inbound webhook receiver URL on instanode.dev. Returns a receive_url that accepts any HTTP method from any sender and stores each request (method, headers, body, received_at). GET the same URL to pull back the stored log. The 'name' field is required. Useful for: testing Stripe/GitHub/Slack webhooks locally, inspecting payloads during development, building integrations without exposing a local port. Without INSTANODE_TOKEN: free tier — up to 100 requests stored, 24h TTL. With INSTANODE_TOKEN (paid): 1000 stored, permanent.. It is categorised as a Write tool in the Instanode MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for create_webhook. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Instanode MCP server.
create_webhook 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 rule in your Intercept 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 Intercept policy for create_webhook. 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 is provided by the Instanode MCP server (@instanode/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept