cf_update_dns_record · Cargoshipper MCP: Risk & Policy

WHAT IT DOES

What cf_update_dns_record does on Cargoshipper

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

WHY IT NEEDS A POLICY

Why cf_update_dns_record needs a policy

DNS record updates are Write operations—they modify existing records reversibly without permanent deletion. However, DNS changes have high blast radius: incorrect updates can redirect traffic, break services, enable phishing, or cause widespread outages affecting multiple applications/users.

From the tool's definition Tool name is 'cf_update_dns_record' with empty description. Based on sibling tools like cf_create_dns_record, cf_delete_dns_record, and cf_get_dns_records, this operates on CloudFlare DNS records. The 'update' operation modifies DNS configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cf_update_dns_record Rate-limited

cf_update_dns_record 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": {
    "cf_update_dns_record": {
      "limits": [
        {
          "counter": "cf_update_dns_record_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 Cargoshipper, so you can run agents against it safely.

FAQ

Questions about cf_update_dns_record

What does the cf_update_dns_record tool do? +

cf_update_dns_record. It is categorised as a Write tool in the Cargoshipper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cf_update_dns_record? +

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

What risk level is cf_update_dns_record? +

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

Can I rate-limit cf_update_dns_record? +

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

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

cf_update_dns_record is provided by the Cargoshipper MCP server (scarr7981/cargoshipper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.