Opsphere — DevOps & SRE Intelligence

Cloudflare: Config Rules replace

cf_config_rules_replace

Destructive

Replace Configuration Rules entrypoint (http_config_settings) with the provided full rules array.

Input Schema

Name	Required	Description
`zone`	Yes	Zone name (e.g. your-tenant.com) or zone ID
`rules`	Yes	Complete Cloudflare configuration rules array
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`description`	No
`account_slug`	No	Cloudflare account slug. Required when the workspace has multiple accounts and the zone is not yet cataloged.
`environment_slug`	No	Cloud Catalog environment used as an account-routing preference when no zone is provided.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / data / properties / count
```
Removed value: -{
-  "type": "number"
-}
```
addedOutput schema / properties / data / properties / description
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / data / properties / errors / items / $ref
```
Removed value: -"#/properties/data/properties/result/anyOf/0/items"
```
addedOutput schema / properties / data / properties / errors / items / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / data / properties / errors / items / properties

Added value: +{
+  "code": {
+    "type": "integer"
+  },
+  "message": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / data / properties / errors / items / required
```
Added value: +[
+  "message"
+]
```
addedOutput schema / properties / data / properties / errors / items / type
```
Added value: +"object"
```

addedOutput schema / properties / data / properties / gaps

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / id
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / data / properties / items

Removed value: -{
-  "$ref": "#/properties/data/properties/result/anyOf/0"
-}

addedOutput schema / properties / data / properties / lastUpdated

Added value: +{
+  "format": "date-time",
+  "type": "string"
+}

removedOutput schema / properties / data / properties / messages

Removed value: -{
-  "items": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "$ref": "#/properties/data/properties/result/anyOf/0/items"
-      }
-    ]
-  },
-  "type": "array"
-}

addedOutput schema / properties / data / properties / name
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / data / properties / phase
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / data / properties / result

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "additionalProperties": true,
-        "properties": {},
-        "type": "object"
-      },
-      "type": "array"
-    },
-    {
-      "$ref": "#/properties/data/properties/result/anyOf/0/items"
-    }
-  ]
-}

removedOutput schema / properties / data / properties / result_info

Removed value: -{
-  "$ref": "#/properties/data/properties/result/anyOf/0/items"
-}

addedOutput schema / properties / data / properties / rules

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "type": "string"
+      },
+      "childRulesetId": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "enabled": {
+        "type": "boolean"
+      },
+      "expression": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "ref": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "enabled"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / data / properties / version
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / data / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / required

Added value: +[
+  "rules",
+  "partial",
+  "truncated",
+  "warnings",
+  "gaps"
+]

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 2,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

B3.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the bar is lower. The description adds real value by clarifying that this is a full overwrite of the entrypoint (not a merge or patch), but says nothing about what existing rules are lost, ordering requirements, or any prerequisite read-modify-write flow.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, no filler, and the destructive overwrite semantics are front-loaded via the verb 'Replace'. It is close to minimal but leaves the reader wanting one more clause about prerequisites.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained. However, for a destructive full-replacement tool with six parameters including account/environment routing, the description omits the crucial workflow context (read current rules first via cf_config_rules_list) and any account-routing notes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83%, so most parameters are already documented in the schema. The description reinforces that 'rules' must be the complete array rather than a delta, which is genuinely useful, but adds nothing about zone vs. account_slug vs. environment_slug routing logic.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb plus resource: 'Replace Configuration Rules entrypoint (http_config_settings)' names the exact Cloudflare entrypoint being written. It doesn't distinguish itself from adjacent siblings like cf_config_rules_list or cf_ruleset_entrypoint_update, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this versus cf_config_rules_list (to read current state first) or the other *_rules_replace siblings. The phrase 'with the provided full rules array' hints that a complete array is required, but the agent must infer this rather than being told.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Opsphere — DevOps & SRE Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?