vibecontrols_devportal_apps_webhooks_add
Add a webhook to an application. The live mutation takes applicationId as a top-level argument plus input: CreateWebhookInput!. The result is WebhookCreated { webhook { ... } } (the type itself has no id).
This record as markdown: /tools/vibecontrols-mcp/vibecontrols-devportal-apps-webhooks-add.md
What vibecontrols_devportal_apps_webhooks_add does on Vibecontrols
AI agents use vibecontrols_devportal_apps_webhooks_add to create or update resources in Vibecontrols, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vibecontrols environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Delivery URL |
name | string | Yes | Webhook name |
events | array | Yes | Event names |
maxRetries | number | — | Default 5 |
applicationId | string | Yes | Application ID |
Parameters from the server's own tool schema.
Why vibecontrols_devportal_apps_webhooks_add is rated Medium
An AI agent can call vibecontrols_devportal_apps_webhooks_add faster than any human can review: one bad instruction and it creates or modifies resources in Vibecontrols by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs vibecontrols_devportal_apps_webhooks_add safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vibecontrols, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vibecontrols_devportal_apps_webhooks_add, this is the rule to start with:
vibecontrols_devportal_apps_webhooks_add 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Vibecontrols, apply this rule, and every vibecontrols_devportal_apps_webhooks_add call is checked against it from then on.
Questions about vibecontrols_devportal_apps_webhooks_add
Add a webhook to an application. The live mutation takes applicationId as a top-level argument plus input: CreateWebhookInput!. The result is WebhookCreated { webhook { ... } } (the type itself has no id). It is categorised as a Write tool in the Vibecontrols MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
vibecontrols_devportal_apps_webhooks_add accepts 5 parameters: url, name, events, maxRetries, applicationId. Required: url, name, events, applicationId. The full parameter table on this page comes from the server's own tool schema.
Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_devportal_apps_webhooks_add: 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 Vibecontrols. Nothing to install.
vibecontrols_devportal_apps_webhooks_add 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 vibecontrols_devportal_apps_webhooks_add 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 vibecontrols_devportal_apps_webhooks_add. 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.
vibecontrols_devportal_apps_webhooks_add is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vibecontrols, and thousands of servers like it.
This server
Across the catalogue