update_webhook
Update an outbound webhook subscription URL, events, active flag, description, or filter expression.
This record as markdown: /tools/adrata-starfield-mcp/update-webhook.md
What update_webhook does on Starfield
AI agents use update_webhook to create or update resources in Starfield, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Starfield environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Webhook subscription ID |
url | string | — | |
active | boolean | — | |
events | array | — | |
description | string | — | |
filterExpression | object | — |
Parameters from the server's own tool schema.
Why update_webhook is rated Medium
An AI agent can call update_webhook faster than any human can review: one bad instruction and it creates or modifies resources in Starfield 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 update_webhook safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_webhook, this is the rule to start with:
update_webhook 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 Starfield, apply this rule, and every update_webhook call is checked against it from then on.
Questions about update_webhook
Update an outbound webhook subscription URL, events, active flag, description, or filter expression. It is categorised as a Write tool in the Starfield MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_webhook accepts 6 parameters: id, url, active, events, description, filterExpression. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Starfield 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 Starfield. 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 Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Starfield, and thousands of servers like it.
This server
Across the catalogue