endpoint_delete_many

endpoint \u00b7 DELETE /endpoint/deleteMany \u2014 Disable instance of the objects. Required: q. Requires a JSON request body.

Server Vicarius vRx MCP Server space-c0wboy/vicarius-vrx-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What endpoint_delete_many does on Vicarius vRx MCP Server

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

Why endpoint_delete_many needs a policy

This tool performs batch deletion of endpoint objects. Although the description uses the word 'Disable' rather than 'delete', the HTTP method (DELETE) and endpoint naming convention clearly indicate data removal. Deleting or disabling endpoint instances cannot be undone and represents a destructive operation with significant blast radius if invoked incorrectly by an AI agent.

From the tool's definition Tool name is 'endpoint_delete_many' and description states 'DELETE /endpoint/deleteMany — Disable instance of the objects.' The DELETE HTTP method combined with 'deleteMany' in the tool name and endpoint path indicates irreversible deletion of multiple…

Questions about endpoint_delete_many

What does the endpoint_delete_many tool do? +

endpoint \u00b7 DELETE /endpoint/deleteMany \u2014 Disable instance of the objects. Required: q. Requires a JSON request body. It is categorised as a Destructive tool in the Vicarius vRx 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 endpoint_delete_many? +

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

What risk level is endpoint_delete_many? +

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

Yes. Add a rate_limit block to the endpoint_delete_many 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 endpoint_delete_many completely? +

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

endpoint_delete_many is provided by the Vicarius vRx MCP Server MCP server (space-c0wboy/vicarius-vrx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.