Low Risk

get_device_counters

Get device counters and statistics

How to control get_device_counters ↓

What get_device_counters does on SD-WAN MCP Server

AI agents call get_device_counters 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.

Low Risk

Why get_device_counters needs a policy

This tool retrieves device performance metrics and statistical counters from SD-WAN devices. It performs a read-only query with no side effects, no code execution, no data modification, and no irreversible actions. The blast radius of misuse is minimal—an attacker could gather operational intelligence about network devices but cannot modify, delete, or disrupt actual network operations.

From the tool's definition Tool name 'get_device_counters' and description 'Get device counters and statistics' indicate retrieval of metrics and monitoring data.

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

How to control get_device_counters

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_device_counters": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_device_counters

What does the get_device_counters tool do? +

Get device counters and statistics. 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_device_counters? +

Register the SD-WAN MCP Server MCP server in PolicyLayer and add a rule for get_device_counters: 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_device_counters? +

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

Can I rate-limit get_device_counters? +

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

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

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

Free to start. No card required.

18 SD-WAN MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.