webhook_endpoint_create · Omise MCP Server MCP

WHAT IT DOES

What webhook_endpoint_create does on Omise MCP Server

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

WHY IT NEEDS A POLICY

Why webhook_endpoint_create needs a policy

Creating a webhook endpoint writes configuration data to the system. While reversible (endpoints can be deleted), this is a sensitive operation because webhooks can expose data to external URLs and could be configured to send payment/customer data to attacker-controlled endpoints. Misuse could lead to credential leakage, data exfiltration, or notification interception.

From the tool's definition Tool name 'webhook_endpoint_create' and description 'Create a new webhook endpoint' indicate creation of a new webhook endpoint resource. This modifies the system configuration by adding a new webhook, which is a reversible Write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

webhook_endpoint_create Rate-limited

webhook_endpoint_create 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": {
    "webhook_endpoint_create": {
      "limits": [
        {
          "counter": "webhook_endpoint_create_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 Omise MCP Server, so you can run agents against it safely.

FAQ

Questions about webhook_endpoint_create

What does the webhook_endpoint_create tool do? +

Create a new webhook endpoint. It is categorised as a Write tool in the Omise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on webhook_endpoint_create? +

Register the Omise MCP Server MCP server in PolicyLayer and add a rule for webhook_endpoint_create: 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 Omise MCP Server. Nothing to install.

What risk level is webhook_endpoint_create? +

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

Can I rate-limit webhook_endpoint_create? +

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

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

webhook_endpoint_create is provided by the Omise MCP Server MCP server (jun-omise/omise-mcp-alpha). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.