create_trusted_redirect_domain
Create a new trusted redirect domain
This record as markdown: /tools/adbutler/create-trusted-redirect-domain.md
What create_trusted_redirect_domain does on AdButler
AI agents use create_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 |
|---|---|---|---|
domain | string | Yes | Trusted redirect domain (e.g. example.com) |
Parameters from the server's own tool schema.
Why create_trusted_redirect_domain is rated Medium
This tool creates a new domain configuration in the AdButler advertising platform. While creation is reversible (domains can be deleted or modified), creating a trusted redirect domain could have downstream effects on ad tracking and redirection behavior if misconfigured.
From the tool's definition Tool description explicitly states 'Create a new trusted redirect domain', indicating creation of a new resource/configuration entry.
Attacks that exploit this kind of access
The rule that runs create_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 create_trusted_redirect_domain, this is the rule to start with:
create_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 create_trusted_redirect_domain call is checked against it from then on.
Questions about create_trusted_redirect_domain
Create a new 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.
create_trusted_redirect_domain accepts 1 parameter: domain. Required: domain. 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 create_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.
create_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 create_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 create_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.
create_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