Sets the webhook URL for this Monobank token. Monobank will send real-time push notifications to this URL for every new transaction.\n\nWARNING: Each token supports only one webhook URL. Calling this tool overwrites the existing URL with no confirmation. Use monobank-get-webhook to check the curr...
AI agents use monobank-set-webhook to create or update resources in Monobank — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Monobank environment.
This tool modifies configuration state by setting a webhook URL, which is a reversible write operation. However, it has high severity because: (1) it overwrites existing configuration without confirmation, creating a potential denial-of-service or hijacking risk if an AI agent sets a malicious webhook URL; (2) webhook URLs control where sensitive transaction notifications are sent, so misconfiguration could redirect…
From the tool's definition Sets the webhook URL for this Monobank token. Calling this tool overwrites the existing URL with no confirmation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Sets the webhook URL for this Monobank token. Monobank will send real-time push notifications to this URL for every new transaction.\n\nWARNING: Each token supports only one webhook URL. Calling this tool overwrites the existing URL with no confirmation. Use monobank-get-webhook to check the current value first. It is categorised as a Write tool in the Monobank MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Monobank MCP server in PolicyLayer and add a rule for monobank-set-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 Monobank. Nothing to install.
monobank-set-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 monobank-set-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 monobank-set-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.
monobank-set-webhook is provided by the Monobank MCP server (todesstoss/monobank-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
monobank-set-webhook is one line of Monobank's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →