This record as markdown: /tools/aapanel-mcp/site-set-ssl.md
What site_set_ssl does on Aapanel
AI agents use site_set_ssl 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 site_set_ssl is rated Medium
This tool modifies a site's SSL certificate configuration, which is a reversible change (certificates can be replaced or updated). It does not destroy data (Destructive), execute arbitrary code (Execute), or move money (Financial).
From the tool's definition Tool name 'site_set_ssl' with description 'Deploy SSL certificate to a site' indicates modification of site security configuration. 'Deploy' and 'set' are Write operations that modify existing site settings.
Attacks that exploit this kind of access
The rule that runs site_set_ssl 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 site_set_ssl, this is the rule to start with:
site_set_ssl 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 site_set_ssl call is checked against it from then on.
Questions about site_set_ssl
Deploy 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 site_set_ssl: 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.
site_set_ssl 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 site_set_ssl 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 site_set_ssl. 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.
site_set_ssl 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