ssl_save_cert
Save/upload an SSL certificate to the panel.
This record as markdown: /tools/aapanel-mcp/ssl-save-cert.md
What ssl_save_cert does on Aapanel
AI agents use ssl_save_cert 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 ssl_save_cert is rated Medium
This tool creates or modifies SSL certificate data stored on the panel, qualifying as Write rather than Read (retrieves) or Execute (runs code). The severity is high because compromised or malicious SSL certificates could enable man-in-the-middle attacks, impersonate legitimate services, or redirect traffic.
From the tool's definition ssl_save_cert: 'Save/upload an SSL certificate to the panel' — explicitly modifies system SSL certificate storage by writing data to the panel infrastructure.
Attacks that exploit this kind of access
The rule that runs ssl_save_cert 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 ssl_save_cert, this is the rule to start with:
ssl_save_cert 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 ssl_save_cert call is checked against it from then on.
Questions about ssl_save_cert
Save/upload an SSL certificate to the panel. 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 ssl_save_cert: 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.
ssl_save_cert 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 ssl_save_cert 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 ssl_save_cert. 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.
ssl_save_cert 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