update_whois_contact · Domain Suite MCP: Risk & Policy

WHAT IT DOES

What update_whois_contact does on Domain Suite

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

WHY IT NEEDS A POLICY

Why update_whois_contact needs a policy

This is a Write operation because it updates/modifies WHOIS contact details reversibly. While not destructive (the change can be reverted), it ranks as 'high' severity because unauthorized modification of domain contact information could enable domain theft, impersonate the domain owner, redirect email communications, or facilitate account takeover. The blast radius is significant for domain security and control.

From the tool's definition Tool name is 'update_whois_contact' and description states 'Update domain WHOIS contact'. This modifies (creates or updates) domain registration contact information, which is reversible but sensitive personal data tied to domain ownership.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_whois_contact Rate-limited

update_whois_contact 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": {
    "update_whois_contact": {
      "limits": [
        {
          "counter": "update_whois_contact_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Domain Suite, so you can run agents against it safely.

FAQ

Questions about update_whois_contact

What does the update_whois_contact tool do? +

Update domain WHOIS contact. It is categorised as a Write tool in the Domain Suite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_whois_contact? +

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

What risk level is update_whois_contact? +

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

Can I rate-limit update_whois_contact? +

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

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

update_whois_contact is provided by the Domain Suite MCP server (oso95/domain-suite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.