open_staking_position
Stake INDY tokens by creating a new staking position. Returns an unsigned transaction (CBOR hex) for client-side signing.
This record as markdown: /tools/indigoprotocol-indigo-mcp/open-staking-position.md
What open_staking_position does on Indigo Protocol MCP
AI agents use open_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 |
|---|---|---|---|
amount | string | — | INDY amount to stake (in smallest unit) |
address | string | — | User Cardano bech32 address |
Parameters from the server's own tool schema.
Why open_staking_position is rated Medium
This tool writes/creates a new staking position by generating an unsigned transaction. It is Write rather than Execute because the transaction requires client-side signing before execution, and rather than Financial because staking is a commitment of tokens (not a direct payment or trade).
From the tool's definition Tool description states it creates a new staking position and returns an unsigned transaction for signing. 'Creating' a staking position is a reversible write operation that modifies the user's staking state.
Attacks that exploit this kind of access
The rule that runs open_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 open_staking_position, this is the rule to start with:
open_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Indigo Protocol MCP, apply this rule, and every open_staking_position call is checked against it from then on.
Questions about open_staking_position
Stake INDY tokens by creating a new staking position. 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.
open_staking_position accepts 2 parameters: amount, address. The full parameter table on this page comes from the server's own tool schema.
Register the Indigo Protocol MCP server in PolicyLayer and add a rule for open_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.
open_staking_position is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the open_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.
Set action: deny in the PolicyLayer policy for open_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.
open_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.
More on Indigo Protocol, and thousands of servers like it.
This server
Across the catalogue