site_force_https
Force HTTP to HTTPS redirect for a site.
This record as markdown: /tools/aapanel-mcp/site-force-https.md
What site_force_https does on Aapanel
AI agents use site_force_https 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_force_https is rated Medium
This tool modifies the site's configuration to enforce HTTPS redirects. It is a reversible configuration change (the redirect can be disabled), so it falls under Write rather than Destructive. Misuse could disrupt site accessibility if misconfigured, giving it medium severity.
From the tool's definition Force HTTP to HTTPS redirect for a site
Attacks that exploit this kind of access
The rule that runs site_force_https 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_force_https, this is the rule to start with:
site_force_https 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_force_https call is checked against it from then on.
Questions about site_force_https
Force HTTP to HTTPS redirect for 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_force_https: 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_force_https 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_force_https 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_force_https. 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_force_https 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