get_physical_interfaces

Get all physical interfaces for a specific node

Server Claude-Modeling-Labs MCP Server mediocretriumph/claude-cml-toolkit
Category Read
Risk class Low
Parameters 00 required

What get_physical_interfaces does on Claude-Modeling-Labs MCP Server

AI agents call get_physical_interfaces to retrieve information from Claude-Modeling-Labs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_physical_interfaces needs a policy

This tool queries existing network topology data within Cisco Modeling Labs and returns interface information. It performs no modifications, deletions, executions, or financial transactions. The blast radius of misuse is minimal—an agent could only retrieve information it may not be authorized to see, which is a low-severity data exposure risk.

From the tool's definition Tool name 'get_physical_interfaces' and description 'Get all physical interfaces for a specific node' indicate a query/retrieval operation with no side effects. The verb 'get' and action of retrieving interface information confirms read-only behavior.

Questions about get_physical_interfaces

What does the get_physical_interfaces tool do? +

Get all physical interfaces for a specific node. It is categorised as a Read tool in the Claude-Modeling-Labs MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_physical_interfaces? +

Register the Claude-Modeling-Labs MCP Server MCP server in PolicyLayer and add a rule for get_physical_interfaces: 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 Claude-Modeling-Labs MCP Server. Nothing to install.

What risk level is get_physical_interfaces? +

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

Can I rate-limit get_physical_interfaces? +

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

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

get_physical_interfaces is provided by the Claude-Modeling-Labs MCP Server MCP server (mediocretriumph/claude-cml-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.