Low Risk

get_device_platform

Retrieve platform information for a specific device in Cisco NSO. Requires a

How to control get_device_platform ↓

What get_device_platform does on Cisco NSO MCP Server

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

Low Risk

Why get_device_platform needs a policy

This tool retrieves platform information from Cisco NSO without creating, modifying, or deleting data. It is a straightforward data query operation with no side effects. The low severity reflects minimal blast radius—an AI agent retrieving platform details poses negligible risk. Confidence is high because the name and description explicitly indicate a retrieval/read operation.

From the tool's definition Tool name 'get_device_platform' and description 'Retrieve platform information for a specific device in Cisco NSO' indicate a read-only query operation that fetches device metadata without modification.

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

How to control get_device_platform

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

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

get_device_platform 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 Cisco NSO 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_platform

What does the get_device_platform tool do? +

Retrieve platform information for a specific device in Cisco NSO. Requires a. It is categorised as a Read tool in the Cisco NSO MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_device_platform? +

Register the Cisco NSO MCP Server MCP server in PolicyLayer and add a rule for get_device_platform: 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.

What risk level is get_device_platform? +

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

Can I rate-limit get_device_platform? +

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

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

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

Enforce policy on every Cisco NSO MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.