domains_records

Get the DNS records the user needs to configure at their DNS provider. Call after domains_set. You MUST show the returned records to the user.

Part of the ShipStatic MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@shipstatic/mcp Write Risk 2/5

// WHEN AI AGENTS USE THIS TOOL

AI agents use domains_records to create or modify resources in ShipStatic. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON DOMAINS_RECORDS

Without a policy, an AI agent could call domains_records repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach ShipStatic.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

shipstatic.yaml

tools:
  domains_records:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full ShipStatic policy for all 15 tools.

// DETAILS

Tool Name domains_records

Category Write

MCP Server ShipStatic MCP Server

Risk Level Medium

// MORE SHIPSTATIC TOOLS

Destructive deployments_remove Destructive domains_remove Write deployments_set Write deployments_upload Write domains_dns Write domains_set Read deployments_get Read deployments_list

View all 15 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like domains_records have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the domains_records tool do? +

Get the DNS records the user needs to configure at their DNS provider. Call after domains_set. You MUST show the returned records to the user.. It is categorised as a Write tool in the ShipStatic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on domains_records? +

Add a rule in your Intercept YAML policy under the tools section for domains_records. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the ShipStatic MCP server.

What risk level is domains_records? +

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

Can I rate-limit domains_records? +

Yes. Add a rate_limit block to the domains_records rule in your Intercept 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 domains_records completely? +

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

domains_records is provided by the ShipStatic MCP server (@shipstatic/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

domains_records

Enforce policies on ShipStatic