管理 CloudBase 静态托管的变更操作。action=upload 上传本地构建产物到共享域名（域名格式：<envId>-<appId>.tcloudbaseapp.com/<cloudPath>）；action=delete 删除托管文件或目录（必须 confirm=true）；action=setWebsiteDocument 设置首页/错误页/路由规则；action=enableService 开通静态托管；action=bindDomain / unbindDomain / updateDomain 管理自定义域名；action=downloadFile / downloa...
AI agents call manageHosting to permanently remove resources in CloudBase MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool encompasses multiple operations including file/directory deletion (irreversible), domain unbinding, and overwriting hosted content via upload. Per the severity rules, the most severe applicable category is Destructive due to the delete and unbindDomain actions that cannot be undone.
From the tool's definition action=delete 删除托管文件或目录（必须 confirm=true）; action=upload 上传本地构建产物; action=unbindDomain; action=updateDomain — spans destructive deletion and irreversible domain changes
Documented attack patterns abuse exactly the kind of access manageHosting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CloudBase MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for manageHosting:
{
"version": "1",
"default": "deny",
"hide": [
"manageHosting"
]
}manageHosting disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
管理 CloudBase 静态托管的变更操作。action=upload 上传本地构建产物到共享域名（域名格式：<envId>-<appId>.tcloudbaseapp.com/<cloudPath>）；action=delete 删除托管文件或目录（必须 confirm=true）；action=setWebsiteDocument 设置首页/错误页/路由规则；action=enableService 开通静态托管；action=bindDomain / unbindDomain / updateDomain 管理自定义域名；action=downloadFile / downloadDirectory 下载托管内容到本地。⚠️ 新项目部署优先使用 manageApps（部署到独立子域名），本工具适合已有老项目继续使用或作为 manageApps 的 fallback。manageApps 与 manageHosting 域名不同，切换会导致老链接失效。若任务只是查看配置、文件或域名状态，请改用 queryHosting。. It is categorised as a Destructive tool in the CloudBase MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CloudBase MCP server in PolicyLayer and add a rule for manageHosting: 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 CloudBase MCP. Nothing to install.
manageHosting is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the manageHosting 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 manageHosting. 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.
manageHosting is provided by the CloudBase MCP server (tencentcloudbase/cloudbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 CloudBase MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 CloudBase MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.