Critical Risk →

cancel_lrp

Cancel an existing LRP position. Returns an unsigned transaction (CBOR hex) for client-side signing.

Part of the Indigo Protocol MCP server.

cancel_lrp can permanently delete data in Indigo Protocol MCP, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE INDIGO PROTOCOL MCP →

Free to start. No card required.

AI agents may call cancel_lrp to permanently remove or destroy resources in Indigo Protocol MCP. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call cancel_lrp in a loop, permanently destroying resources in Indigo Protocol MCP. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_lrp"
  ]
}

See the full Indigo Protocol MCP policy for all 62 tools.

Get this rule live on your own Indigo Protocol MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY INDIGO PROTOCOL MCP →

View all 62 tools →

These attack patterns abuse exactly the kind of access cancel_lrp gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so cancel_lrp only ever does what you allow.

SECURE INDIGO PROTOCOL MCP →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the cancel_lrp tool do? +

Cancel an existing LRP position. Returns an unsigned transaction (CBOR hex) for client-side signing.. It is categorised as a Destructive tool in the Indigo Protocol MCP 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 cancel_lrp? +

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

What risk level is cancel_lrp? +

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

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

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

cancel_lrp is provided by the Indigo Protocol MCP server (indigoprotocol/indigo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Indigo Protocol MCP tool call.

Deterministic rules across all 62 Indigo Protocol MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.