pay_webhook_register

SERVERPay Mcp SOURCE@pay-skill/mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pay-skill-pay-mcp/pay-webhook-register.md

WHAT IT DOES

What pay_webhook_register does on Pay Mcp

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

RISK

Why pay_webhook_register is rated Medium

Registering a webhook is a Write operation: it creates a persistent configuration record (a webhook endpoint) in the system. While it exists in a financial server context, the tool itself does not move money or commit financial obligations — it merely sets up a notification listener. It is reversible (webhooks can be unregistered).

From the tool's definition 'Register a webhook to receive real-time payment event notifications' — this creates a new webhook registration entry

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pay_webhook_register safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pay Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pay_webhook_register, this is the rule to start with:

pay_webhook_register Rate-limited

pay_webhook_register 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": {
    "pay_webhook_register": {
      "limits": [
        {
          "counter": "pay_webhook_register_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pay Mcp, apply this rule, and every pay_webhook_register call is checked against it from then on.

FAQ

Questions about pay_webhook_register

What does the pay_webhook_register tool do? +

Register a webhook to receive real-time payment event notifications.\n\n. It is categorised as a Write tool in the Pay Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pay_webhook_register? +

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

What risk level is pay_webhook_register? +

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

Can I rate-limit pay_webhook_register? +

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

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

pay_webhook_register is provided by the Pay MCP server (@pay-skill/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pay, and thousands of servers like it.

This server

All 15 Pay tools →

Across the catalogue

team_manager_register_agents on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →