New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

revokeCollectionShare

DELETE /v1/collections/{collection_id}/shares/{share_id}

SERVERVipcasso SOURCE@vipcasso/mcp
Critical RISK CLASS
Category Destructive
Parameters 50 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vipcasso-mcp/revokecollectionshare.md

What revokeCollectionShare does on Vipcasso

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

ParameterTypeRequiredDescription
body object —
files array —
query object —
fields object —
path_params object —

Parameters from the server's own tool schema.

Why revokeCollectionShare is rated Critical

An AI agent that decides to call revokeCollectionShare doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Vipcasso is gone. There is no undo for destructive operations.

Risk signalsAccepts file system path (files[].filename) · Accepts raw HTML/template content (body)

Questions about revokeCollectionShare

What does the revokeCollectionShare tool do? +

DELETE /v1/collections/{collection_id}/shares/{share_id}. It is categorised as a Destructive tool in the Vipcasso MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does revokeCollectionShare accept? +

revokeCollectionShare accepts 5 parameters: body, files, query, fields, path_params. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on revokeCollectionShare? +

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

What risk level is revokeCollectionShare? +

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

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

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

revokeCollectionShare is provided by the Vipcasso MCP server (@vipcasso/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Vipcasso, 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 Vipcasso'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.