Set service cluster policy
set_service_cluster_policyDeclare a cluster's managed-service placement policy (the twin of ankra services policy set): the physical region it runs in (for example eu-north-1) and the data boundary its data may stay within (for example eu), which decides which consumers a service on it may serve. Declaring one is optional: a cluster without one is set up under the open default (unspecified), and once declared, every setup on the cluster is held to it; unspecified is reserved and cannot be declared. expected_revision is the policy's current revision from get_service_cluster_policy, or 0 to create it. Requires clusters.write.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"cluster_id": "<cluster_id>",
"region": "<region>",
"data_boundary": "<data_boundary>",
"expected_revision": "<expected_revision>"
},
"name": "set_service_cluster_policy"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| region | Yes | Physical cloud region of the cluster, for example eu-north-1. It locates infrastructure; it is not the data-location promise. | |
| cluster_id | Yes | Cluster id (UUID) from list_clusters. | |
| local_only | No | true when data on this cluster must stay on it. Defaults to false. | |
| data_boundary | Yes | Boundary the data is permitted to stay within, for example eu. Sharing a service across clusters is decided by this, never by the region. | |
| expected_revision | Yes | The policy's current revision from get_service_cluster_policy; 0 creates a policy and is refused when one exists. |