edgeconnect_set_next_zone_id

Set the next available EdgeConnect firewall-zone ID with write guards.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/edgeconnect-set-next-zone-id.md

WHAT IT DOES

What edgeconnect_set_next_zone_id does on API-Central

AI agents use edgeconnect_set_next_zone_id 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.

RISK

Why edgeconnect_set_next_zone_id is rated Medium

This tool modifies firewall zone IDs on EdgeConnect appliances, which is a configuration change that affects network security posture. While reversible and guarded, misconfiguration could segment traffic incorrectly or create security gaps. Severity is 'high' rather than 'critical' because the operation is bounded to zone ID assignment (not wholesale network disruption) and includes protective guards.

From the tool's definition Tool name includes 'set_' indicating modification; description states 'Set the next available EdgeConnect firewall-zone ID' which creates or modifies firewall zone configuration. Presence of 'write guards' suggests reversibility and explicit safety measures.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs edgeconnect_set_next_zone_id safely

PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For edgeconnect_set_next_zone_id, this is the rule to start with:

edgeconnect_set_next_zone_id Rate-limited

edgeconnect_set_next_zone_id 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": {
    "edgeconnect_set_next_zone_id": {
      "limits": [
        {
          "counter": "edgeconnect_set_next_zone_id_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every edgeconnect_set_next_zone_id call is checked against it from then on.

FAQ

Questions about edgeconnect_set_next_zone_id

What does the edgeconnect_set_next_zone_id tool do? +

Set the next available EdgeConnect firewall-zone ID with write guards. 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 edgeconnect_set_next_zone_id? +

Register the API-Central MCP server in PolicyLayer and add a rule for edgeconnect_set_next_zone_id: 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 edgeconnect_set_next_zone_id? +

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

Can I rate-limit edgeconnect_set_next_zone_id? +

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

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

edgeconnect_set_next_zone_id 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.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →