monobank-unset-webhook · Monobank MCP: Risk & Policy

WHAT IT DOES

What monobank-unset-webhook does on Monobank

AI agents use monobank-unset-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.

WHY IT NEEDS A POLICY

Why monobank-unset-webhook needs a policy

This tool modifies webhook configuration by removing/unsetting a previously configured URL. While it doesn't delete user data or execute arbitrary code, it does change the notification delivery state of the account. The operation is reversible (a new webhook can be set), placing it in the Write category.

From the tool's definition The tool description states it 'Removes the webhook URL' which is a modification operation. It explicitly mentions that calling this action stops Monobank from sending push notifications, indicating a state change in the webhook configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

monobank-unset-webhook Rate-limited

monobank-unset-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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "monobank-unset-webhook": {
      "limits": [
        {
          "counter": "monobank-unset-webhook_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Monobank, so you can run agents against it safely.

FAQ

Questions about monobank-unset-webhook

What does the monobank-unset-webhook tool do? +

Removes the webhook URL for this Monobank token. Monobank will stop sending push notifications. Safe to call even if no webhook is currently set. 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.

How do I enforce a policy on monobank-unset-webhook? +

Register the Monobank MCP server in PolicyLayer and add a rule for monobank-unset-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.

What risk level is monobank-unset-webhook? +

monobank-unset-webhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit monobank-unset-webhook? +

Yes. Add a rate_limit block to the monobank-unset-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.

How do I block monobank-unset-webhook completely? +

Set action: deny in the PolicyLayer policy for monobank-unset-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.

What MCP server provides monobank-unset-webhook? +

monobank-unset-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.