AI agents call cloud_delete_invitation to permanently remove resources in MCP ClickHouse — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (an invitation record) and cannot be undone. While the blast radius is not as critical as deleting core infrastructure or services, it does permanently remove an entity from the system. The action cannot be reversed without administrative intervention.
From the tool's definition Tool name is 'cloud_delete_invitation' and description states 'Delete/cancel an invitation.' The verb 'delete' combined with the irreversible action of removing an invitation record meets the definition of Destructive.
Documented attack patterns abuse exactly the kind of access cloud_delete_invitation gives an agent:
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_invitation:
{
"version": "1",
"default": "deny",
"hide": [
"cloud_delete_invitation"
]
} cloud_delete_invitation 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.
Delete/cancel an invitation. 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.
Register the MCP ClickHouse MCP server in PolicyLayer and add a rule for cloud_delete_invitation: 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.
cloud_delete_invitation 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 cloud_delete_invitation 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 cloud_delete_invitation. 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.
cloud_delete_invitation 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.
Start from MCP ClickHouse, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
55 MCP ClickHouse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.