disable_webhook · Kula Ai MCP: Risk & Policy

WHAT IT DOES

What disable_webhook does on Kula Ai

AI agents use disable_webhook to create or update resources in Kula Ai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kula Ai environment.

WHY IT NEEDS A POLICY

Why disable_webhook needs a policy

The tool modifies webhook configuration state rather than irreversibly deleting it. It is reversible (the webhook can be re-enabled), placing it in the Write category rather than Destructive. Severity is medium because disabling webhooks could disrupt event notifications and integrations, affecting recruiting workflows, but the action is not destructive and can be undone.

From the tool's definition disable_webhook disables an active webhook, which modifies its state (active → disabled) reversibly. This is a configuration change that does not permanently delete data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disable_webhook Rate-limited

disable_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": {
    "disable_webhook": {
      "limits": [
        {
          "counter": "disable_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 Kula Ai, so you can run agents against it safely.

FAQ

Questions about disable_webhook

What does the disable_webhook tool do? +

Disable an active webhook. It is categorised as a Write tool in the Kula Ai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disable_webhook? +

Register the Kula Ai MCP server in PolicyLayer and add a rule for disable_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 Kula Ai. Nothing to install.

What risk level is disable_webhook? +

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

Can I rate-limit disable_webhook? +

Yes. Add a rate_limit block to the disable_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 disable_webhook completely? +

Set action: deny in the PolicyLayer policy for disable_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 disable_webhook? +

disable_webhook is provided by the Kula Ai MCP server (kula-ai/kula-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.