This record as markdown: /tools/io-github-pay-skill-pay-mcp/pay-webhook-list.md
What pay_webhook_list does on Pay Mcp
AI agents call pay_webhook_list to retrieve information from Pay Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pay_webhook_list is rated Low
This tool retrieves configuration data (webhooks) associated with a user's wallet. It performs a read-only operation with no side effects, no code execution, no data modification, and no financial movement. While the parent server handles financial operations, this specific tool merely lists existing webhook configurations without executing them or making payments.
From the tool's definition Tool name 'pay_webhook_list' and description 'List all registered webhooks for your wallet' indicate a query/retrieval operation with no modification or financial transaction.
Attacks that exploit this kind of access
The rule that runs pay_webhook_list 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_list, this is the rule to start with:
pay_webhook_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pay Mcp, apply this rule, and every pay_webhook_list call is checked against it from then on.
Questions about pay_webhook_list
List all registered webhooks for your wallet. It is categorised as a Read tool in the Pay Mcp MCP Server, which means it retrieves data without modifying state.
Register the Pay MCP server in PolicyLayer and add a rule for pay_webhook_list: 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.
pay_webhook_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pay_webhook_list 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.
Set action: deny in the PolicyLayer policy for pay_webhook_list. 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.
pay_webhook_list 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.
More on Pay, and thousands of servers like it.
This server
Across the catalogue