webhook_endpoint_update · Omise MCP Server MCP

WHAT IT DOES

What webhook_endpoint_update does on Omise MCP Server

AI agents use webhook_endpoint_update 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_update needs a policy

This tool creates or modifies webhook endpoint configuration reversibly (can be updated again or reverted). It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve data (Read).

From the tool's definition Tool name 'webhook_endpoint_update' and description 'Update webhook endpoint information' indicate modification of webhook configuration data. This modifies webhook settings which are critical infrastructure components for payment processing systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

webhook_endpoint_update Rate-limited

webhook_endpoint_update 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_update": {
      "limits": [
        {
          "counter": "webhook_endpoint_update_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_update

What does the webhook_endpoint_update tool do? +

Update webhook endpoint information. 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_update? +

Register the Omise MCP Server MCP server in PolicyLayer and add a rule for webhook_endpoint_update: 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_update? +

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

Can I rate-limit webhook_endpoint_update? +

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

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

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