close_staking_position

Close an INDY staking position and unstake all INDY. Returns an unsigned transaction (CBOR hex) for client-side signing.

SERVERIndigo Protocol MCP SOURCEindigoprotocol/indigo-mcp

Medium RISK CLASS

Category Write

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/indigoprotocol-indigo-mcp/close-staking-position.md

WHAT IT DOES

What close_staking_position does on Indigo Protocol MCP

AI agents use close_staking_position to create or update resources in Indigo Protocol MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Indigo Protocol MCP environment.

Parameter	Type	Required	Description
`address`	string	—	User Cardano bech32 address
`positionTxHash`	string	—	Transaction hash of the staking position UTxO
`positionOutputIndex`	number	—	Output index of the staking position UTxO

Parameters from the server's own tool schema.

RISK

Why close_staking_position is rated Medium

This tool creates a transaction that modifies the user's staking position by closing it and unstaking INDY tokens. While it involves cryptocurrency/financial assets, it is reversible (users can re-stake), does not move funds to external parties (unstaking returns to user), and does not result in permanent loss. The tool returns an unsigned transaction requiring client-side signing, so execution is not immediate.

From the tool's definition Tool description states 'Close an INDY staking position and unstake all INDY' and 'Returns an unsigned transaction'. This modifies financial positions by closing/unstaking assets.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs close_staking_position safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Indigo Protocol MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_staking_position, this is the rule to start with:

close_staking_position Rate-limited

close_staking_position stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_staking_position": {
      "limits": [
        {
          "counter": "close_staking_position_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Indigo Protocol MCP, apply this rule, and every close_staking_position call is checked against it from then on.

FAQ

Questions about close_staking_position

What does the close_staking_position tool do? +

Close an INDY staking position and unstake all INDY. Returns an unsigned transaction (CBOR hex) for client-side signing. It is categorised as a Write tool in the Indigo Protocol MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does close_staking_position accept? +

close_staking_position accepts 3 parameters: address, positionTxHash, positionOutputIndex. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on close_staking_position? +

Register the Indigo Protocol MCP server in PolicyLayer and add a rule for close_staking_position: 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 close_staking_position? +

close_staking_position is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit close_staking_position? +

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

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

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

KEEP EXPLORING

More on Indigo Protocol, and thousands of servers like it.

This server

All 62 Indigo Protocol tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →