动态添加服务器配置
AI agents use add_server_config to create or update resources in MCP SSH Tools Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP SSH Tools Server environment.
This tool creates or modifies server configuration entries, which is a Write operation. Severity is high because misconfigured SSH credentials or malicious server entries could enable unauthorized access, lateral movement, or credential theft. The reversibility (configs can be updated/removed) and lack of immediate data destruction place it in Write rather than Destructive.
From the tool's definition Tool name 'add_server_config' and description '动态添加服务器配置' (dynamically add server configuration) indicates creation/modification of configuration data. Sibling tools show this server manages SSH connections and server credentials.
Attacks that exploit this kind of access
动态添加服务器配置. It is categorised as a Write tool in the MCP SSH Tools Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP SSH Tools Server MCP server in PolicyLayer and add a rule for add_server_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 MCP SSH Tools Server. Nothing to install.
add_server_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_server_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 add_server_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.
add_server_config is provided by the MCP SSH Tools Server MCP server (nwnusun-cool/mcp-server-ssh-tools). 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 →