DeleteV1InstancesById

THE RISK

Critical Risk

Why DeleteV1InstancesById needs a policy

This tool performs irreversible deletion of payment infrastructure instances. In the context of BlindPay's stablecoin payment system, an instance represents a core operational entity that manages receivers, wallets, transactions, and user accounts. Deletion is non-recoverable and would cause complete loss of that instance's data and operations.

From the tool's definition Tool name 'DeleteV1InstancesById' combined with description 'Delete Instance' indicates irreversible deletion of an entire instance—a core infrastructure component.

Documented attack patterns abuse exactly the kind of access DeleteV1InstancesById gives an agent:

POLICY

How to control DeleteV1InstancesById

PolicyLayer is an MCP gateway — it sits between your AI agents and BlindPay MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for DeleteV1InstancesById:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "DeleteV1InstancesById"
  ]
}

DeleteV1InstancesById disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register BlindPay MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More BlindPay MCP Server tools

Financial PostV1InstancesTransferQuotes Create Transfer Quote Financial PostV1InstancesCreateAssetTrustline Create Asset Trustline Financial PostV1InstancesMintUsdbSolana Mint USDB on Solana Financial PostV1InstancesMintUsdbStellar Mint USDB on Stellar Financial PostV1InstancesPayinQuotes Create Payin Quote Financial PostV1InstancesPayinsEvm Create Payin Financial PostV1InstancesPayoutsEvm Create Payout on EVM Chains Financial PostV1InstancesPayoutsSolana Create Payout on Solana

All 81 BlindPay MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Govern database agents → Read-only defaults, blocked table drops, and no DELETE without a WHERE clause on every query.
Critical-risk tools in BlindPay MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about DeleteV1InstancesById

What does the DeleteV1InstancesById tool do? +

Delete Instance. It is categorised as a Destructive tool in the BlindPay 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 DeleteV1InstancesById? +

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

What risk level is DeleteV1InstancesById? +

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

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

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

DeleteV1InstancesById is provided by the BlindPay MCP Server MCP server (blindpaylabs/blindpay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BlindPay MCP Server tool call.

Start from BlindPay MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →