update_domain_contacts · Spaceship MCP: Risk & Policy

WHAT IT DOES

What update_domain_contacts does on Spaceship

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

WHY IT NEEDS A POLICY

Why update_domain_contacts needs a policy

This tool modifies domain administrative and contact metadata, which are critical to domain ownership and control. While the change is reversible (contacts can be updated again), unauthorized modification could redirect domain control, compromise security, or enable takeover attacks.

From the tool's definition Tool updates domain contacts (registrant, admin, tech, billing) for a specific domain, modifying existing contact information associated with domain records. The description explicitly states 'Update' which indicates reversible modification of data.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_domain_contacts Rate-limited

update_domain_contacts 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_domain_contacts": {
      "limits": [
        {
          "counter": "update_domain_contacts_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 Spaceship, so you can run agents against it safely.

FAQ

Questions about update_domain_contacts

What does the update_domain_contacts tool do? +

Update the contacts (registrant, admin, tech, billing) for a specific domain using contact IDs. It is categorised as a Write tool in the Spaceship 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_domain_contacts? +

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

What risk level is update_domain_contacts? +

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

Can I rate-limit update_domain_contacts? +

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

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

update_domain_contacts is provided by the Spaceship MCP server (naveenkm007/spaceship-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.