Update a specific zone setting
AI agents use cf_update_zone_setting 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.
This tool modifies zone settings (DNS configuration, security policies, performance rules, etc.) in CloudFlare. Updates are reversible (unlike deletions), placing it in Write rather than Destructive. However, severity is high because misconfigured zone settings could disrupt DNS resolution, disable security features, or degrade service availability across all domains in the zone.
From the tool's definition Tool name contains 'update' and description states 'Update a specific zone setting' — modifies configuration data for DNS zones in CloudFlare.
Attacks that exploit this kind of access
Update a specific zone setting. 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.
Register the Cargoshipper MCP server in PolicyLayer and add a rule for cf_update_zone_setting: 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.
cf_update_zone_setting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cf_update_zone_setting 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.
Set action: deny in the PolicyLayer policy for cf_update_zone_setting. 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.
cf_update_zone_setting 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →