gcp_agent_delete_endpoint

Delete a Vertex AI endpoint

SERVERGCP MCP Server SOURCEahmedselimmansor-ctrl/gcp_mcp_server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-agent-delete-endpoint.md

What gcp_agent_delete_endpoint does on GCP MCP Server

AI agents call gcp_agent_delete_endpoint to permanently remove resources in GCP MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why gcp_agent_delete_endpoint is rated Critical

Deletion of endpoints is a destructive action that cannot be undone. The endpoint and any deployed models on it would be destroyed, severing access to AI services. This affects infrastructure availability and business continuity. An AI agent with this capability could halt production services if misused, making it critical severity.

From the tool's definition Tool name contains 'delete' and description states 'Delete a Vertex AI endpoint' — irreversible deletion of infrastructure

Questions about gcp_agent_delete_endpoint

What does the gcp_agent_delete_endpoint tool do? +

Delete a Vertex AI endpoint. It is categorised as a Destructive tool in the GCP MCP Server 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 gcp_agent_delete_endpoint? +

Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_agent_delete_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 GCP MCP Server. Nothing to install.

What risk level is gcp_agent_delete_endpoint? +

gcp_agent_delete_endpoint 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 gcp_agent_delete_endpoint? +

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

How do I block gcp_agent_delete_endpoint completely? +

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

What MCP server provides gcp_agent_delete_endpoint? +

gcp_agent_delete_endpoint is provided by the GCP MCP Server MCP server (ahmedselimmansor-ctrl/gcp_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GCP MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GCP MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.