Get the public webhook URL for configuring in Bitnovo Pay Dashboard. Returns the complete webhook URL that should be configured as the notification_url in your Bitnovo device settings. This URL includes the tunnel provider information (ngrok, zrok, or manual). The webhook URL is automatically gen...
AI agents call get_webhook_url to retrieve information from Sperax Ecosystem Crypto & DeFI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves webhook configuration information for use in external dashboard setup. It performs no data creation, modification, deletion, code execution, or financial operations. The purpose is to query and return the current webhook URL based on execution context, making it a straightforward Read operation with minimal security risk.
From the tool's definition Tool description states it 'Get[s] the public webhook URL' and 'Returns the complete webhook URL' — purely retrieves configuration information with no side effects. The tool reads and returns existing webhook URL configuration data.
Documented attack patterns abuse exactly the kind of access get_webhook_url gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_webhook_url:
{
"version": "1",
"default": "deny",
"tools": {
"get_webhook_url": {}
}
}get_webhook_url is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the public webhook URL for configuring in Bitnovo Pay Dashboard. Returns the complete webhook URL that should be configured as the notification_url in your Bitnovo device settings. This URL includes the tunnel provider information (ngrok, zrok, or manual). The webhook URL is automatically generated based on your execution context: - Local development: Uses ngrok or zrok tunnel with persistent URL - N8N/Opal/VPS: Uses the configured WEBHOOK_PUBLIC_URL - Server environments: Auto-detects and provides appropriate URL Important: After receiving this URL, configure it in Bitnovo Dashboard: 1. Log into https://pay.bitnovo.com 2. Navigate to: Settings → Merchant → Devices 3. Select your device 4. Set. It is categorised as a Read tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for get_webhook_url: 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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
get_webhook_url 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 get_webhook_url 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 get_webhook_url. 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.
get_webhook_url is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.