AI agents call get_device_alerts 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 existing alert and warning information from SD-WAN devices. It queries data without side effects, no code execution, no data modification, and no destructive operations. Consistent with sibling tools like 'get_device_health_summary', 'get_device_counters', and 'get_bfd_sessions' which are all pure read operations.
From the tool's definition Tool name 'get_device_alerts' and description 'Get alerts and warnings for devices' indicate retrieval of alert/warning data with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access get_device_alerts 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_device_alerts:
{
"version": "1",
"default": "deny",
"tools": {
"get_device_alerts": {}
}
}get_device_alerts 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 alerts and warnings for devices. 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_device_alerts: 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_device_alerts 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_device_alerts 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_device_alerts. 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_device_alerts 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.