dynadot_restore

Restore a deleted domain (within the redemption period).

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-restore.md

WHAT IT DOES

What dynadot_restore does on Dynadot

AI agents use dynadot_restore 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_restore is rated Medium

While restoration might superficially resemble an undo operation, it is fundamentally a Write action because it modifies domain state by changing it from 'deleted' to 'active'. This is reversible (the domain can be deleted again), so it does not qualify as Destructive.

From the tool's definition Tool description states 'Restore a deleted domain (within the redemption period)' — this reverses a deletion by recovering a domain that was deleted, which is a data modification action that restores a previous state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dynadot_restore 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_restore, this is the rule to start with:

dynadot_restore Rate-limited

dynadot_restore 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_restore": {
      "limits": [
        {
          "counter": "dynadot_restore_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_restore call is checked against it from then on.

FAQ

Questions about dynadot_restore

What does the dynadot_restore tool do? +

Restore a deleted domain (within the redemption period). 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_restore? +

Register the Dynadot MCP server in PolicyLayer and add a rule for dynadot_restore: 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_restore? +

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

Can I rate-limit dynadot_restore? +

Yes. Add a rate_limit block to the dynadot_restore 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_restore completely? +

Set action: deny in the PolicyLayer policy for dynadot_restore. 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_restore? +

dynadot_restore 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

The MCP Attack Database →

Guides

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