automation_task_templates_delete_many

automation_task_templates \u00b7 DELETE /automationTaskTemplates/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 automation_task_templates_delete_many does on Vicarius vRx MCP Server

AI agents call automation_task_templates_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 automation_task_templates_delete_many needs a policy

This tool performs irreversible deletion of multiple automation task template objects via a DELETE API endpoint. Although the description says 'Disable instance' (which might suggest soft-delete), the explicit DELETE method and 'deleteMany' operation name indicate destructive action that cannot be undone.

From the tool's definition DELETE /automationTaskTemplates/deleteMany — Disable instance of the objects. The HTTP method is DELETE and the operation is 'deleteMany', indicating bulk deletion of automation task templates.

Questions about automation_task_templates_delete_many

What does the automation_task_templates_delete_many tool do? +

automation_task_templates \u00b7 DELETE /automationTaskTemplates/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 automation_task_templates_delete_many? +

Register the Vicarius vRx MCP Server MCP server in PolicyLayer and add a rule for automation_task_templates_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 automation_task_templates_delete_many? +

automation_task_templates_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 automation_task_templates_delete_many? +

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

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

automation_task_templates_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.