Update an existing webhook
AI agents use update_webhook to create or update resources in Airtable MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Airtable MCP Server environment.
Updating a webhook modifies existing configuration data but does not delete it (which would be Destructive) nor execute arbitrary code directly (which would be Execute). It is a Write operation because it alters webhook settings reversibly.
From the tool's definition Tool name and description: 'update_webhook' / 'Update an existing webhook'. Webhooks are configuration objects that trigger external HTTP callbacks; modifying them changes their behavior, target URL, or event subscriptions—a reversible operation.
Attacks that exploit this kind of access
Update an existing webhook. It is categorised as a Write tool in the Airtable MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Airtable MCP Server MCP server in PolicyLayer and add a rule for update_webhook: 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 Airtable MCP Server. Nothing to install.
update_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 update_webhook 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 update_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.
update_webhook is provided by the Airtable MCP Server MCP server (loticdigital/airtable-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →