Retrieve the available Network Element Driver (NED) IDs in Cisco NSO.
AI agents call get_device_ned_ids to retrieve information from Cisco NSO MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about available NEDs in NSO. It performs read-only introspection of the system's configuration or state without side effects. The presence of similar read operations (get_device_config, get_device_groups, get_device_platform, get_device_state, get_service_types, get_services) on the same server confirms the pattern.
From the tool's definition Tool name 'get_device_ned_ids' contains 'get' and description states 'Retrieve the available Network Element Driver (NED) IDs' — a pure retrieval operation with no modification, deletion, or execution of external commands.
Documented attack patterns abuse exactly the kind of access get_device_ned_ids gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cisco NSO MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_device_ned_ids:
{
"version": "1",
"default": "deny",
"tools": {
"get_device_ned_ids": {}
}
}get_device_ned_ids 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.
Retrieve the available Network Element Driver (NED) IDs in Cisco NSO. It is categorised as a Read tool in the Cisco NSO MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cisco NSO MCP Server MCP server in PolicyLayer and add a rule for get_device_ned_ids: 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 Cisco NSO MCP Server. Nothing to install.
get_device_ned_ids 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_ned_ids 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_ned_ids. 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_ned_ids is provided by the Cisco NSO MCP Server MCP server (nso-developer/cisco-nso-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cisco NSO 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.
9 Cisco NSO MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.