Register a webhook endpoint to receive real-time notifications when QR codes are scanned. Returns an HMAC-SHA256 secret for verifying webhook signatures — store it securely, it is only shown once.
AI agents use create_webhook to create or update resources in QR for Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QR for Agent environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | The endpoint URL that will receive POST requests with scan event data. |
events | array | — | Events to subscribe to. Currently supported: "qr.scanned". |
Parameters from the server's own tool schema.
This tool creates (writes) a webhook configuration and generates a cryptographic secret, which modifies the system state. It is not Read (it writes/persists data), not Destructive (the webhook can typically be unregistered), not Execute in the classical sense (it doesn't run arbitrary code or shell commands), not Financial.
From the tool's definition The tool "Register a webhook endpoint" creates a new webhook configuration and generates a secret credential. These are persistent, non-reversible state changes (the webhook registration persists; the secret is only shown once).
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Register a webhook endpoint to receive real-time notifications when QR codes are scanned. Returns an HMAC-SHA256 secret for verifying webhook signatures — store it securely, it is only shown once. It is categorised as a Write tool in the QR for Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_webhook accepts 2 parameters: url, events. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the QR for Agent MCP server in PolicyLayer and add a rule for create_webhook: 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 QR for Agent. Nothing to install.
create_webhook 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 create_webhook 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 create_webhook. 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.
create_webhook is provided by the QR for Agent MCP server (qr-for-agent). 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 →