update_trusted_redirect_domain
Update an existing trusted redirect domain
This record as markdown: /tools/adbutler/update-trusted-redirect-domain.md
What update_trusted_redirect_domain does on AdButler
AI agents use update_trusted_redirect_domain to create or update resources in AdButler, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Trusted redirect domain ID |
domain | string | — | Trusted redirect domain (e.g. example.com) |
Parameters from the server's own tool schema.
Why update_trusted_redirect_domain is rated Medium
This tool modifies AdButler campaign/domain configuration in a reversible manner. While domain whitelist changes could have downstream effects on ad delivery, the action itself is a write operation that can be undone.
From the tool's definition Tool name 'update_trusted_redirect_domain' and description 'Update an existing trusted redirect domain' indicate modification of configuration data. The 'update' verb confirms reversible data change rather than deletion or execution of arbitrary operations.
Attacks that exploit this kind of access
The rule that runs update_trusted_redirect_domain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_trusted_redirect_domain, this is the rule to start with:
update_trusted_redirect_domain stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every update_trusted_redirect_domain call is checked against it from then on.
Questions about update_trusted_redirect_domain
Update an existing trusted redirect domain. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_trusted_redirect_domain accepts 2 parameters: id, domain. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for update_trusted_redirect_domain: 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 AdButler. Nothing to install.
update_trusted_redirect_domain 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 update_trusted_redirect_domain 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 update_trusted_redirect_domain. 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.
update_trusted_redirect_domain is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue