[Pro tier] Create, list, or delete webhooks for real-time RWA event notifications. Supports events: transfer.large, mint.detected, burn.detected, supply.change, token.new, price.alert. Free keys receive 401 with upgrade URL.
AI agents use manage_webhooks to create or update resources in RWA Pipe MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RWA Pipe MCP Server environment.
The tool performs both write operations (create webhooks) and destructive operations (delete webhooks). However, webhook deletion is reversible through recreation, and webhooks are configuration metadata rather than primary data assets.
From the tool's definition Tool can 'Create, list, or delete webhooks' for event notifications. Creation and deletion of webhooks are reversible write operations on notification infrastructure.
Attacks that exploit this kind of access
[Pro tier] Create, list, or delete webhooks for real-time RWA event notifications. Supports events: transfer.large, mint.detected, burn.detected, supply.change, token.new, price.alert. Free keys receive 401 with upgrade URL. It is categorised as a Write tool in the RWA Pipe MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RWA Pipe MCP Server MCP server in PolicyLayer and add a rule for manage_webhooks: 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 RWA Pipe MCP Server. Nothing to install.
manage_webhooks is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_webhooks 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 manage_webhooks. 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.
manage_webhooks is provided by the RWA Pipe MCP Server MCP server (rwapipe/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →