send_config
AI agents invoke send_config to trigger actions in Netmiko 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.
The tool name 'send_config' strongly implies it sends configuration commands to network devices via SSH. Configuration changes on network devices (routers, switches, firewalls) can have wide blast radius effects — disrupting connectivity, altering security policies, or causing outages. This falls under Execute as it triggers external operations on remote devices.
From the tool's definition Tool name 'send_config' on a server described as 'supporting command execution, configuration management' via SSH using Netmiko; sibling tools include 'send_command' and 'send_config_parallel'
Attacks that exploit this kind of access
send_config. It is categorised as a Execute tool in the Netmiko MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Netmiko MCP Server MCP server in PolicyLayer and add a rule for send_config: 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 Netmiko MCP Server. Nothing to install.
send_config 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_config 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_config. 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_config is provided by the Netmiko MCP Server MCP server (ntunes/netmiko-mcp-server). 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 →