This record as markdown: /tools/aapanel-mcp/ssh-get-security-status.md
What ssh_get_security_status does on Aapanel
AI agents call ssh_get_security_status to retrieve information from Aapanel without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ssh_get_security_status is rated Low
This tool retrieves SSH security audit status information. It has no side effects, does not modify any system state, and does not execute commands or operations. It is a pure read operation that queries existing security audit data, making it a Read category tool with low severity.
From the tool's definition Tool name 'ssh_get_security_status' and description 'Get SSH security audit status' indicate a retrieval operation. The verb 'get' and noun 'status' reflect querying/reading existing audit information without modification.
Attacks that exploit this kind of access
The rule that runs ssh_get_security_status 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_get_security_status, this is the rule to start with:
ssh_get_security_status is read-only, so it stays allowed. 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_get_security_status call is checked against it from then on.
Questions about ssh_get_security_status
Get SSH security audit status. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.
Register the Aapanel MCP server in PolicyLayer and add a rule for ssh_get_security_status: 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_get_security_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ssh_get_security_status 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_get_security_status. 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_get_security_status 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