cloud_delete_query_endpoint_config

THE RISK

Critical Risk

Why cloud_delete_query_endpoint_config needs a policy

This tool irreversibly deletes a query endpoint configuration, which is a destructive operation. While not as critical as deleting an entire service or data, removing endpoint configuration can disrupt service availability and query routing. The 'experimental' flag suggests potential instability, but does not reduce the destructive nature of the action.

From the tool's definition Tool name contains 'delete' and description states 'Delete query endpoint configuration' — these are explicit indicators of irreversible deletion. The configuration deletion cannot be undone and will remove access/routing settings for a service.

Documented attack patterns abuse exactly the kind of access cloud_delete_query_endpoint_config gives an agent:

POLICY

How to control cloud_delete_query_endpoint_config

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP ClickHouse, and nothing reaches the server without passing your rules. This is the rule we recommend for cloud_delete_query_endpoint_config:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cloud_delete_query_endpoint_config"
  ]
}

cloud_delete_query_endpoint_config disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register MCP ClickHouse — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP ClickHouse tools

Destructive cloud_delete_api_key Delete an API key. Destructive cloud_delete_clickpipe Delete a ClickPipe. Destructive cloud_delete_invitation Delete/cancel an invitation. Destructive cloud_delete_reverse_private_endpoint Delete a reverse private endpoint (beta). Destructive cloud_delete_service Delete a service (must be stopped first). Destructive cloud_remove_member Remove a member from the organization. Execute run_query Run a query in a ClickHouse database. Execute cloud_update_clickpipe_state Start, stop, or resync a ClickPipe.

All 55 MCP ClickHouse tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MCP ClickHouse → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cloud_delete_query_endpoint_config

What does the cloud_delete_query_endpoint_config tool do? +

Delete query endpoint configuration for a service (experimental). It is categorised as a Destructive tool in the MCP ClickHouse MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cloud_delete_query_endpoint_config? +

Register the MCP ClickHouse MCP server in PolicyLayer and add a rule for cloud_delete_query_endpoint_config: 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 MCP ClickHouse. Nothing to install.

What risk level is cloud_delete_query_endpoint_config? +

cloud_delete_query_endpoint_config is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cloud_delete_query_endpoint_config? +

Yes. Add a rate_limit block to the cloud_delete_query_endpoint_config 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.

How do I block cloud_delete_query_endpoint_config completely? +

Set action: deny in the PolicyLayer policy for cloud_delete_query_endpoint_config. 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.

What MCP server provides cloud_delete_query_endpoint_config? +

cloud_delete_query_endpoint_config is provided by the MCP ClickHouse MCP server (oualib/chmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP ClickHouse tool call.

Start from MCP ClickHouse, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →