enable_webhook · Kula Ai MCP: Risk & Policy

WHAT IT DOES

What enable_webhook does on Kula Ai

AI agents use enable_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 enable_webhook needs a policy

Enabling a webhook is a Write operation—it modifies resource state but is reversible (the webhook can be disabled again). While webhooks can trigger external operations, the tool itself only changes the webhook's enabled/disabled flag, not the webhook's destination URL or execution logic.

From the tool's definition Tool is named 'enable_webhook' and described as 'Enable a disabled webhook.' This modifies the state of an existing webhook resource by changing its disabled status to enabled, which is a reversible configuration change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

enable_webhook Rate-limited

enable_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": {
    "enable_webhook": {
      "limits": [
        {
          "counter": "enable_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 enable_webhook

What does the enable_webhook tool do? +

Enable a disabled 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 enable_webhook? +

Register the Kula Ai MCP server in PolicyLayer and add a rule for enable_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 enable_webhook? +

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

Can I rate-limit enable_webhook? +

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

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

enable_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.