This record as markdown: /tools/io-github-portel-dev-ncp/webhook-create.md
What webhook_create does on Ncp
AI agents use webhook_create to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why webhook_create is rated Medium
Creating a webhook is a reversible write operation that establishes a new integration endpoint. While it modifies Airtable configuration, it does not delete data, execute arbitrary code, or move money. The severity is medium because a misconfigured webhook could expose data or trigger unintended actions, but the operation itself is not inherently destructive or financial.
From the tool's definition Tool name 'webhook_create' and description 'Create Airtable webhook' indicate creation of a new webhook resource in Airtable. This is a write operation that modifies configuration state.
Attacks that exploit this kind of access
The rule that runs webhook_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For webhook_create, this is the rule to start with:
webhook_create 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 Ncp, apply this rule, and every webhook_create call is checked against it from then on.
Questions about webhook_create
Create Airtable webhook. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for webhook_create: 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 Ncp. Nothing to install.
webhook_create 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 webhook_create 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 webhook_create. 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.
webhook_create is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue