Send a command to a node console
AI agents invoke send_console_command to trigger actions in Claude-Modeling-Labs MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending commands to a network node console constitutes remote execution on network devices. Depending on the command, this could configure, disrupt, or destroy network topologies. The blast radius is high because an AI agent could issue destructive or misconfiguring commands (e.g., shutdown interfaces, erase configs, delete routes) across simulated or even real network infrastructure.
From the tool's definition 'Send a command to a node console' — this tool executes arbitrary commands on network device consoles in a live lab environment.
Attacks that exploit this kind of access
Send a command to a node console. It is categorised as a Execute tool in the Claude-Modeling-Labs MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude-Modeling-Labs MCP Server MCP server in PolicyLayer and add a rule for send_console_command: 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.
send_console_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_console_command 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 send_console_command. 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.
send_console_command 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.
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 →