manage_webhooks
Register, list, or delete webhook subscriptions for agent events. Requires api_key for register/delete.
This record as markdown: /tools/io-github-wirternow-agent-bank/manage-webhooks.md
What manage_webhooks does on Ai Agent Bank
AI agents use manage_webhooks to create or update resources in Ai Agent Bank, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ai Agent Bank environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | Webhook ID to delete (delete) |
action | string | Yes | register, list, or delete |
api_key | string | — | Your api_key (required for register/delete) |
agent_id | string | — | UUID of the agent (register/list) |
event_type | string | — | Event type (register) |
webhook_url | string | — | URL to receive POST (register) |
Parameters from the server's own tool schema.
Why manage_webhooks is rated Medium
The tool primarily performs reversible configuration management (registering and deleting webhooks). While it includes read capability (list), the key operations are write-class: creating new webhook subscriptions and removing them. This is not destructive data deletion (those would be financial records or wallets), nor does it directly move funds.
From the tool's definition Tool description states it can 'Register, list, or delete webhook subscriptions' — the register and delete operations are write/modification actions that alter webhook configurations.
Risk signalsAccepts URL/endpoint input (webhook_url) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs manage_webhooks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ai Agent Bank, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manage_webhooks, this is the rule to start with:
manage_webhooks 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 Ai Agent Bank, apply this rule, and every manage_webhooks call is checked against it from then on.
Questions about manage_webhooks
Register, list, or delete webhook subscriptions for agent events. Requires api_key for register/delete. It is categorised as a Write tool in the Ai Agent Bank MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
manage_webhooks accepts 6 parameters: id, action, api_key, agent_id, event_type, webhook_url. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Ai Agent Bank MCP server in PolicyLayer and add a rule for manage_webhooks: 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 Ai Agent Bank. Nothing to install.
manage_webhooks 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 manage_webhooks 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 manage_webhooks. 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.
manage_webhooks is provided by the Ai Agent Bank MCP server (https://tdueqhfxyojmjgactdyc.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ai Agent Bank, and thousands of servers like it.
This server
Across the catalogue