Acknowledge processed webhook events
AI agents use webhook_ack to create or update resources in Shellgate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shellgate environment.
Acknowledging a webhook event is a write/state-change operation: it marks events as processed, which is reversible in principle but changes state on the server. It does not execute code, delete data, or move money. Severity is medium because misuse could cause events to be incorrectly marked as processed, potentially disrupting integrations or causing missed processing of important events.
From the tool's definition Acknowledge processed webhook events
Documented attack patterns abuse exactly the kind of access webhook_ack gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Shellgate, and nothing reaches the server without passing your rules. This is the rule we recommend for webhook_ack:
{
"version": "1",
"default": "deny",
"tools": {
"webhook_ack": {
"limits": [
{
"counter": "webhook_ack_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}webhook_ack 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.
Free to start. No card required.
Acknowledge processed webhook events. It is categorised as a Write tool in the Shellgate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Shellgate MCP server in PolicyLayer and add a rule for webhook_ack: 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 Shellgate. Nothing to install.
webhook_ack 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_ack 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_ack. 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_ack is provided by the Shellgate MCP server (matthiastjong/shellgate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Shellgate, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 Shellgate tools catalogued and risk-classified — across an index of 43,000+ MCP servers.