ssl_set_to_site
Deploy a stored SSL certificate to a site.
This record as markdown: /tools/aapanel-mcp/ssl-set-to-site.md
What ssl_set_to_site does on Aapanel
AI agents use ssl_set_to_site 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_set_to_site is rated Medium
This tool modifies site configuration by applying an SSL certificate, which is a reversible write operation. While it affects site security posture, the action itself can be undone by deploying a different certificate or removing SSL. High severity due to potential for misconfiguration affecting site availability and security, but not destructive since the change is reversible.
From the tool's definition Tool name 'ssl_set_to_site' and description 'Deploy a stored SSL certificate to a site' indicate modification of site configuration. The verb 'deploy' and 'set' confirm data modification.
Attacks that exploit this kind of access
The rule that runs ssl_set_to_site 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_set_to_site, this is the rule to start with:
ssl_set_to_site 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_set_to_site call is checked against it from then on.
Questions about ssl_set_to_site
Deploy a stored SSL certificate to a site. 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_set_to_site: 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_set_to_site 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_set_to_site 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_set_to_site. 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_set_to_site 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