create_gw_cluster · API-Central MCP: Risk & Policy

WHAT IT DOES

What create_gw_cluster does on API-Central

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

WHY IT NEEDS A POLICY

Why create_gw_cluster needs a policy

This tool creates a new gateway cluster profile, which is a data structure modification in the network management system. It qualifies as Write rather than Execute because it creates a discrete configuration object rather than running arbitrary commands.

From the tool's definition Tool name 'create_gw_cluster' and description 'Create an empty gateway cluster profile shell' explicitly indicates creation of a new configuration object.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_gw_cluster Rate-limited

create_gw_cluster 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": {
    "create_gw_cluster": {
      "limits": [
        {
          "counter": "create_gw_cluster_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 API-Central, so you can run agents against it safely.

FAQ

Questions about create_gw_cluster

What does the create_gw_cluster tool do? +

Create an empty gateway cluster profile shell (add members via gateway_join_cluster). It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_gw_cluster? +

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

What risk level is create_gw_cluster? +

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

Can I rate-limit create_gw_cluster? +

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

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

create_gw_cluster is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

create_gw_cluster is one line of API-Central's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →