edgeconnect_set_services
Replace EdgeConnect overlay internet services with write guards.
This record as markdown: /tools/secure-ssid-centralmcp/edgeconnect-set-services.md
What edgeconnect_set_services does on API-Central
AI agents use edgeconnect_set_services 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 edgeconnect_set_services is rated Medium
This tool modifies network overlay service configurations by replacement. While 'Replace' could suggest destructiveness, the mention of 'write guards' indicates the operation is guarded and reversible. The high severity reflects the critical nature of network service configurations—misconfiguration could disrupt network connectivity.
From the tool's definition Tool performs 'Replace EdgeConnect overlay internet services' which modifies network service configuration. The phrase 'Replace' indicates a destructive update operation that overwrites existing service definitions.
Attacks that exploit this kind of access
The rule that runs edgeconnect_set_services 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_services, this is the rule to start with:
edgeconnect_set_services 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.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every edgeconnect_set_services call is checked against it from then on.
Questions about edgeconnect_set_services
Replace EdgeConnect overlay internet services 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.
Register the API-Central MCP server in PolicyLayer and add a rule for edgeconnect_set_services: 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.
edgeconnect_set_services 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 edgeconnect_set_services 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 edgeconnect_set_services. 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.
edgeconnect_set_services 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.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue