edgeconnect_get

Perform a read-only GET request to EdgeConnect Orchestrator API.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/edgeconnect-get.md

WHAT IT DOES

What edgeconnect_get does on API-Central

AI agents call edgeconnect_get to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why edgeconnect_get is rated Low

This tool retrieves data from EdgeConnect Orchestrator API without side effects. However, network orchestrator APIs can expose sensitive configuration and operational data about network topology, security policies, and device states, warranting medium severity due to potential information disclosure risk if an agent misuses access to retrieve confidential network architecture details.

From the tool's definition Tool name contains 'get' and description explicitly states 'read-only GET request'; no modification or execution capabilities mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs edgeconnect_get 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_get, this is the rule to start with:

edgeconnect_get Allowed

edgeconnect_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "edgeconnect_get": {}
  }
}

ALLOW ONLY 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_get call is checked against it from then on.

FAQ

Questions about edgeconnect_get

What does the edgeconnect_get tool do? +

Perform a read-only GET request to EdgeConnect Orchestrator API. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on edgeconnect_get? +

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

edgeconnect_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit edgeconnect_get? +

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

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

edgeconnect_get 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →