dynadot_set_domain_push_request

Push a domain to another Dynadot account.

SERVERDynadot SOURCEeyalm321/dynadot-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eyalm321-dynadot-mcp/dynadot-set-domain-push-request.md

WHAT IT DOES

What dynadot_set_domain_push_request does on Dynadot

AI agents use dynadot_set_domain_push_request to create or update resources in Dynadot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dynadot environment.

RISK

Why dynadot_set_domain_push_request is rated Medium

Pushing a domain to another account modifies the domain's registration state and association, constituting a Write action. It is reversible (unlike a destructive deletion) but has significant blast radius if misused by an AI agent — an attacker could redirect valuable domains to attacker-controlled accounts. This warrants high severity.

From the tool's definition "Push a domain to another Dynadot account" — this modifies domain ownership/association by transferring it to another account, which is a reversible Write operation (it can be pushed back or modified).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dynadot_set_domain_push_request safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dynadot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dynadot_set_domain_push_request, this is the rule to start with:

dynadot_set_domain_push_request Rate-limited

dynadot_set_domain_push_request 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dynadot_set_domain_push_request": {
      "limits": [
        {
          "counter": "dynadot_set_domain_push_request_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dynadot, apply this rule, and every dynadot_set_domain_push_request call is checked against it from then on.

FAQ

Questions about dynadot_set_domain_push_request

What does the dynadot_set_domain_push_request tool do? +

Push a domain to another Dynadot account. It is categorised as a Write tool in the Dynadot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dynadot_set_domain_push_request? +

Register the Dynadot MCP server in PolicyLayer and add a rule for dynadot_set_domain_push_request: 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 Dynadot. Nothing to install.

What risk level is dynadot_set_domain_push_request? +

dynadot_set_domain_push_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dynadot_set_domain_push_request? +

Yes. Add a rate_limit block to the dynadot_set_domain_push_request 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.

How do I block dynadot_set_domain_push_request completely? +

Set action: deny in the PolicyLayer policy for dynadot_set_domain_push_request. 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.

What MCP server provides dynadot_set_domain_push_request? +

dynadot_set_domain_push_request is provided by the Dynadot MCP server (eyalm321/dynadot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dynadot, and thousands of servers like it.

This server

All 105 Dynadot tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →