Low Risk

filter_devices_by_status

Filter devices by operational status

How to control filter_devices_by_status ↓

What filter_devices_by_status does on SD-WAN MCP Server

AI agents call filter_devices_by_status 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 filter_devices_by_status needs a policy

This tool retrieves or filters device information based on status criteria. It performs no data creation, modification, deletion, or external execution. The operation is a standard query/search pattern typical of monitoring and analytics systems. Misuse would be limited to information disclosure with minimal blast radius.

From the tool's definition Tool name 'filter_devices_by_status' and description 'Filter devices by operational status' indicate querying and filtering operations without modifying data.

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

How to control filter_devices_by_status

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

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

filter_devices_by_status 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 filter_devices_by_status

What does the filter_devices_by_status tool do? +

Filter devices by operational status. 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 filter_devices_by_status? +

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

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

Can I rate-limit filter_devices_by_status? +

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

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

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