This record as markdown: /tools/vipcasso-mcp/endaccountaccess.md
What endAccountAccess does on Vipcasso
AI agents call endAccountAccess 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | — | |
files | array | — | |
query | object | — | |
fields | object | — | |
path_params | object | — |
Parameters from the server's own tool schema.
Why endAccountAccess is rated Critical
An AI agent that decides to call endAccountAccess 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)
Attacks that exploit this kind of access
The rule that runs endAccountAccess safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vipcasso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For endAccountAccess, this is the rule to start with:
endAccountAccess is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Vipcasso, apply this rule, and every endAccountAccess call is checked against it from then on.
Questions about endAccountAccess
DELETE /v1/account-access. 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.
endAccountAccess accepts 5 parameters: body, files, query, fields, path_params. The full parameter table on this page comes from the server's own tool schema.
Register the Vipcasso MCP server in PolicyLayer and add a rule for endAccountAccess: 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.
endAccountAccess is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the endAccountAccess 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 endAccountAccess. 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.
endAccountAccess 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.
Across the catalogue