webhook_verify
Verify (or create) webhook signatures for Stripe, GitHub, Slack, Shopify, Twilio, Standard Webhooks / Svix, Paddle, Square, Zoom, Mailgun, Intercom, Linear, Typeform and HubSpot v3, or any generic HMAC scheme — the step agents get wrong when wiring up webhook receivers. Pass the raw body, the rec...
This record as markdown: /tools/com-it-scorptech-x402/webhook-verify.md
What webhook_verify does on ScorpTech x402 API
AI agents call webhook_verify to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | Standard Webhooks / Svix message id when not in headers |
now | integer | — | Unix time for "now" (testing) |
url | string | — | Full webhook URL (Twilio, Square, HubSpot) |
mode | string | — | |
header | string | — | generic: header holding the signature |
method | string | — | HTTP method (HubSpot v3) |
prefix | string | — | generic: prefix before the signature, e.g. "sha256=" |
secret | string | Yes | Signing secret (Stripe whsec_..., Svix whsec_<base64>, ...) |
headers | object | — | Received headers (any case), e.g. {"Stripe-Signature": "t=...,v1=..."} |
payload | string | Yes | The raw request body exactly as received (not re-serialised JSON) |
encoding | string | — | generic: signature encoding |
provider | string | Yes |
Parameters from the server's own tool schema.
Why webhook_verify is rated Low
Even though webhook_verify only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (secret) · Accepts raw HTML/template content (payload) · High parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs webhook_verify safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For webhook_verify, this is the rule to start with:
webhook_verify 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 ScorpTech x402 API, apply this rule, and every webhook_verify call is checked against it from then on.
Questions about webhook_verify
Verify (or create) webhook signatures for Stripe, GitHub, Slack, Shopify, Twilio, Standard Webhooks / Svix, Paddle, Square, Zoom, Mailgun, Intercom, Linear, Typeform and HubSpot v3, or any generic HMAC scheme — the step agents get wrong when wiring up webhook receivers. Pass the raw body, the received headers (or just the signature) and the signing secret: returns valid, the timestamp age against a replay tolerance, and on failure a diagnosis (body re-serialised or trimmed, wrong secret format, hex vs base64, stale timestamp). mode=sign produces the exact headers a provider would send, for testing receivers. Constant-time comparison; the secret is never echoed. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/webhook-verify. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
webhook_verify accepts 12 parameters: id, now, url, mode, header, method, prefix, secret, headers, payload, encoding, provider. Required: secret, payload, provider. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for webhook_verify: 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 ScorpTech x402 API. Nothing to install.
webhook_verify 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 webhook_verify 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 webhook_verify. 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.
webhook_verify is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue