This record as markdown: /tools/aapanel-mcp/ssh-set-info.md
What ssh_set_info does on Aapanel
AI agents use ssh_set_info to create or update resources in Aapanel, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aapanel environment.
Why ssh_set_info is rated Medium
This tool modifies SSH service configuration, which affects system security posture and authentication mechanisms. The changes are reversible (can be reconfigured), making it Write rather than Destructive. However, the blast radius is high because misconfiguration could lock out legitimate access or enable unauthorized access.
From the tool's definition Tool name 'ssh_set_info' combined with description 'Update SSH service configuration' indicates modification of SSH settings, which are critical system configuration files.
Attacks that exploit this kind of access
The rule that runs ssh_set_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ssh_set_info, this is the rule to start with:
ssh_set_info stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every ssh_set_info call is checked against it from then on.
Questions about ssh_set_info
Update SSH service configuration. It is categorised as a Write tool in the Aapanel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aapanel MCP server in PolicyLayer and add a rule for ssh_set_info: 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 Aapanel. Nothing to install.
ssh_set_info 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 ssh_set_info 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 ssh_set_info. 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.
ssh_set_info is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
This server
Across the catalogue