get_fabric_devices

THE RISK

Low Risk

Why get_fabric_devices needs a policy

This tool retrieves a list of fabric devices from the SD-WAN system. It performs a query operation that reads data without side effects, aligning with the Read category. The severity is low because listing devices poses minimal risk—it exposes inventory information but does not enable modification, deletion, or execution of commands.

From the tool's definition Tool name is 'get_fabric_devices' and description states 'Get list of all fabric devices' — a retrieval operation with no modification, deletion, or execution capability.

Documented attack patterns abuse exactly the kind of access get_fabric_devices gives an agent:

POLICY

How to control get_fabric_devices

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_fabric_devices:

policy.json

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

get_fabric_devices is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register SD-WAN MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More SD-WAN MCP Server tools

Write authenticate Authenticate with the SD-WAN management server to establish session Read check_bfd_session_health Monitor BFD session health across all devices Read filter_devices_by_status Filter devices by operational status Read get_bfd_sessions Get BFD sessions for a device Read get_bfd_state Get BFD (Bidirectional Forwarding Detection) state for a device Read get_device_alerts Get alerts and warnings for devices Read get_device_config Get device configuration Read get_device_counters Get device counters and statistics

All 18 SD-WAN MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_fabric_devices

What does the get_fabric_devices tool do? +

Get list of all fabric devices. It is categorised as a Read tool in the SD-WAN MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_fabric_devices? +

Register the SD-WAN MCP Server MCP server in PolicyLayer and add a rule for get_fabric_devices: 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.

What risk level is get_fabric_devices? +

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

Can I rate-limit get_fabric_devices? +

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

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

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

Enforce policy on every SD-WAN MCP Server tool call.

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.

CHECK YOUR STACK →