Get details of a specific reverse private endpoint (beta).
AI agents call cloud_get_reverse_private_endpoint to retrieve information from MCP ClickHouse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves information about an existing reverse private endpoint configuration. It performs a read-only query operation that does not modify, delete, or execute any infrastructure changes. The blast radius of misuse is minimal: an agent could learn details about reverse private endpoint configuration, which is sensitive metadata but not actionable without write/execute permissions on the same server.
From the tool's definition Tool name includes 'get' and description states 'Get details of a specific reverse private endpoint' — this is a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access cloud_get_reverse_private_endpoint 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_get_reverse_private_endpoint:
{
"version": "1",
"default": "deny",
"tools": {
"cloud_get_reverse_private_endpoint": {}
}
} cloud_get_reverse_private_endpoint 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.
Get details of a specific reverse private endpoint (beta). It is categorised as a Read tool in the MCP ClickHouse MCP Server, which means it retrieves data without modifying state.
Register the MCP ClickHouse MCP server in PolicyLayer and add a rule for cloud_get_reverse_private_endpoint: 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_get_reverse_private_endpoint 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 cloud_get_reverse_private_endpoint 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_get_reverse_private_endpoint. 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_get_reverse_private_endpoint 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.