get_trusted_redirect_domain
Get details of a specific trusted redirect domain by ID
This record as markdown: /tools/adbutler/get-trusted-redirect-domain.md
What get_trusted_redirect_domain does on AdButler
AI agents call get_trusted_redirect_domain to retrieve information from AdButler 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 | number | Yes | Trusted redirect domain ID |
Parameters from the server's own tool schema.
Why get_trusted_redirect_domain is rated Low
This tool retrieves configuration details about a trusted redirect domain using an ID parameter. There are no side effects, data modifications, deletions, executions, or financial impacts. It is a straightforward read-only query operation. Severity is low because accessing domain configuration details poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'get_trusted_redirect_domain' and description states 'Get details of a specific trusted redirect domain by ID' — uses 'Get' verb indicating retrieval of existing data with no modifications.
Attacks that exploit this kind of access
The rule that runs get_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 get_trusted_redirect_domain, this is the rule to start with:
get_trusted_redirect_domain 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 AdButler, apply this rule, and every get_trusted_redirect_domain call is checked against it from then on.
Questions about get_trusted_redirect_domain
Get details of a specific trusted redirect domain by ID. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_trusted_redirect_domain accepts 1 parameter: id. 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 get_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.
get_trusted_redirect_domain 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 get_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 get_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.
get_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