查询 CloudBase 静态托管的只读信息。适合 AI 先做发现再决定下一步：action=websiteConfig 查询首页/错误页/路由规则与站点域名信息；action=status 查询托管服务状态；action=findFiles 按前缀查找文件；action=listFiles 列出全部托管文件；action=domainStatus 查询自定义域名的当前状态与配置。该工具不会产生任何副作用。
AI agents call queryHosting to retrieve information from CloudBase MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves configuration and status information about CloudBase hosting without modifying or deleting any data. It is designed for read-only discovery to inform subsequent decisions. The explicit statement that it produces no side effects confirms it belongs in the Read category with low severity.
From the tool's definition Tool description explicitly states '查询 CloudBase 静态托管的只读信息' (query CloudBase static hosting read-only information) and '该工具不会产生任何副作用' (this tool produces no side effects).
Documented attack patterns abuse exactly the kind of access queryHosting 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 queryHosting:
{
"version": "1",
"default": "deny",
"tools": {
"queryHosting": {}
}
}queryHosting is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
查询 CloudBase 静态托管的只读信息。适合 AI 先做发现再决定下一步：action=websiteConfig 查询首页/错误页/路由规则与站点域名信息；action=status 查询托管服务状态；action=findFiles 按前缀查找文件；action=listFiles 列出全部托管文件；action=domainStatus 查询自定义域名的当前状态与配置。该工具不会产生任何副作用。. It is categorised as a Read tool in the CloudBase MCP MCP Server, which means it retrieves data without modifying state.
Register the CloudBase MCP server in PolicyLayer and add a rule for queryHosting: 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.
queryHosting is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the queryHosting 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 queryHosting. 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.
queryHosting 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.