Configure webhook delivery for the developer's app. Webhooks notify your app about subscription lifecycle events (renewals, failures, cancellations). Not required for initial setup — only needed if your app has recurring charges and needs real-time event notifications. Call with webhook_url to se...
AI agents use dev_configure_webhook to create or update resources in Tru — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tru environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
skip | boolean | — | Set to true to skip webhook setup (mark as not needed). |
webhook_url | string | — | The URL where tru should send webhook events (e.g. https://myapp.com/api/tru/webhook). |
Parameters from the server's own tool schema.
This tool modifies application settings (webhook URL configuration) reversibly — the configuration can be changed or cleared later (evidenced by the 'skip=true' option). It does not delete data, execute arbitrary code, or move money, so it falls under Write rather than more severe categories.
From the tool's definition Tool description states: 'Configure webhook delivery' and 'Call with webhook_url to set the URL' — this creates or modifies configuration data (the webhook endpoint).
Risk signalsAccepts URL/endpoint input (webhook_url)
Attacks that exploit this kind of access
Configure webhook delivery for the developer's app. Webhooks notify your app about subscription lifecycle events (renewals, failures, cancellations). Not required for initial setup — only needed if your app has recurring charges and needs real-time event notifications. Call with webhook_url to set the URL and send a test event. Call with skip=true to mark webhooks as not needed. It is categorised as a Write tool in the Tru MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
dev_configure_webhook accepts 2 parameters: skip, webhook_url. The full parameter table on this page comes from the server's own tool schema.
Register the Tru MCP server in PolicyLayer and add a rule for dev_configure_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 Tru. Nothing to install.
dev_configure_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 dev_configure_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 dev_configure_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.
dev_configure_webhook is provided by the Tru MCP server (tru-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 →