Get network topology information based on device connections
AI agents call get_network_topology to retrieve information from SD-WAN MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves network topology information (connections between devices) as a read-only operation. There are no side effects, no code execution, no data modification, and no destructive actions. While network topology could be considered sensitive information that shouldn't be exposed to untrusted actors, the tool itself performs only data retrieval with no ability to affect systems or operations.
From the tool's definition Tool name 'get_network_topology' and description 'Get network topology information based on device connections' indicate a query/retrieval operation that fetches network topology data without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access get_network_topology gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SD-WAN MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_network_topology:
{
"version": "1",
"default": "deny",
"tools": {
"get_network_topology": {}
}
} get_network_topology is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get network topology information based on device connections. It is categorised as a Read tool in the SD-WAN MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SD-WAN MCP Server MCP server in PolicyLayer and add a rule for get_network_topology: 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 SD-WAN MCP Server. Nothing to install.
get_network_topology 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 get_network_topology 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 get_network_topology. 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.
get_network_topology is provided by the SD-WAN MCP Server MCP server (stormbliss/sdwan-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SD-WAN MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 SD-WAN MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.