edgeconnect_get_route_maps
Get EdgeConnect route policy settings for an appliance.
This record as markdown: /tools/secure-ssid-centralmcp/edgeconnect-get-route-maps.md
What edgeconnect_get_route_maps does on API-Central
AI agents call edgeconnect_get_route_maps 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.
Why edgeconnect_get_route_maps is rated Low
This tool queries and retrieves route policy settings from an EdgeConnect appliance. It performs a read-only operation with no side effects, no data modification, and no execution of commands. Misuse would at worst expose network configuration information, which presents minimal risk compared to write, execute, or destructive operations.
From the tool's definition Tool name contains 'get' and description states 'Get EdgeConnect route policy settings' — retrieves configuration data without modification.
Attacks that exploit this kind of access
The rule that runs edgeconnect_get_route_maps 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_route_maps, this is the rule to start with:
edgeconnect_get_route_maps is read-only, so it stays allowed. 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_get_route_maps call is checked against it from then on.
Questions about edgeconnect_get_route_maps
Get EdgeConnect route policy settings for an appliance. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for edgeconnect_get_route_maps: 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_get_route_maps is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the edgeconnect_get_route_maps 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_get_route_maps. 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_get_route_maps 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