# dynadot_set_privacy

Configure WHOIS privacy for a domain.

Agent View of the PolicyLayer registry record for `dynadot_set_privacy`. HTML page: https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-set-privacy

## Facts

- Tool: `dynadot_set_privacy`
- Server: Dynadot (`eyalm321/dynadot-mcp`) — https://policylayer.com/tools/eyalm321-dynadot-mcp.md
- Homepage: https://github.com/Eyalm321/dynadot-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "dynadot_set_privacy",
    "arguments": {}
  }
}
```

## Why dynadot_set_privacy is rated Medium

This tool creates or modifies WHOIS privacy settings for domains, which is a reversible write operation. It does not execute arbitrary code, delete data, transfer financial assets, or perform destructive actions. The potential blast radius is medium because misconfiguration could expose or unnecessarily hide domain ownership information, but the change can be undone.

From the tool's own definition: "Tool description states 'Configure WHOIS privacy for a domain' - this modifies domain privacy settings, which is a reversible configuration change to domain properties."

## Use case

AI agents use dynadot_set_privacy 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Dynadot:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "dynadot_set_privacy": {
      "limits": [
        {
          "counter": "dynadot_set_privacy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Dynadot (104)

- `dynadot_cancel_transfer` — Destructive — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-cancel-transfer.md
- `dynadot_clear_dnssec` — Destructive — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-clear-dnssec.md
- `dynadot_clear_domain_setting` — Destructive — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-clear-domain-setting.md
- `dynadot_delete_backorder_request` — Destructive — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-delete-backorder-request.md
- `dynadot_delete_contact` — Destructive — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-delete-contact.md
- `dynadot_delete_folder` — Destructive — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-delete-folder.md
- `dynadot_delete_ns` — Destructive — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-delete-ns.md
- `dynadot_delete_ns_by_domain` — Destructive — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-delete-ns-by-domain.md
- `dynadot_grace_delete` — Destructive — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-grace-delete.md
- `dynadot_create_cn_audit` — Execute — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-create-cn-audit.md
- `dynadot_authorize_transfer_away` — Financial — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-authorize-transfer-away.md
- `dynadot_bulk_register` — Financial — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-bulk-register.md
- `dynadot_buy_expired_closeout_domain` — Financial — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-buy-expired-closeout-domain.md
- `dynadot_buy_it_now` — Financial — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-buy-it-now.md
- `dynadot_place_auction_bid` — Financial — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-place-auction-bid.md
- `dynadot_place_backorder_auction_bid` — Financial — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-place-backorder-auction-bid.md
- `dynadot_register` — Financial — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-register.md
- `dynadot_renew` — Financial — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-renew.md
- `dynadot_set_afternic_confirm_action` — Financial — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-set-afternic-confirm-action.md
- `dynadot_account_info` — Read — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-account-info.md
- `dynadot_backorder_request_list` — Read — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-backorder-request-list.md
- `dynadot_bulk_search` — Read — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-bulk-search.md
- `dynadot_contact_list` — Read — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-contact-list.md
- `dynadot_domain_appraisal` — Read — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-domain-appraisal.md
- `dynadot_domain_info` — Read — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-domain-info.md
- `dynadot_domain_list` — Read — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-domain-list.md
- `dynadot_download_all_listings` — Read — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-download-all-listings.md
- `dynadot_folder_list` — Read — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-folder-list.md
- `dynadot_get_account_balance` — Read — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-get-account-balance.md
- `dynadot_get_auction_bids` — Read — https://policylayer.com/tools/eyalm321-dynadot-mcp/dynadot-get-auction-bids.md
- …and 74 more: https://policylayer.com/tools/eyalm321-dynadot-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=eyalm321-dynadot-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/eyalm321-dynadot-mcp