This record as markdown: /tools/eaveluo-1panel-mcp/update-https.md
What update_https does on 1Panel MCP Server
AI agents use update_https to create or update resources in 1Panel MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 1Panel MCP Server environment.
Why update_https is rated Medium
The tool modifies (rather than merely reads) HTTPS/SSL settings on server infrastructure. While the changes are technically reversible (unlike a delete operation), incorrect HTTPS configuration can break service availability, expose traffic to downgrade attacks, or disrupt client connectivity.
From the tool's definition Tool name 'update_https' and description 'Update HTTPS configuration' indicate modification of security-critical infrastructure settings.
Attacks that exploit this kind of access
The rule that runs update_https safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_https, this is the rule to start with:
update_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 1Panel MCP Server, apply this rule, and every update_https call is checked against it from then on.
Questions about update_https
Update HTTPS configuration. It is categorised as a Write tool in the 1Panel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for update_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 1Panel MCP Server. Nothing to install.
update_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 update_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 update_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.
update_https is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1Panel MCP Server, and thousands of servers like it.
This server
Across the catalogue