Critical Risk →

adjust_staking_position

Adjust an existing INDY staking position (add or remove INDY). Returns an unsigned transaction (CBOR hex) for client-side signing.

Part of the Indigo MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

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

Without a policy, an AI agent could call adjust_staking_position in a loop, permanently destroying resources in Indigo. There is no undo for destructive operations. Intercept 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.

io-github-indigoprotocol-indigo-mcp.yaml
tools:
  adjust_staking_position:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Indigo policy for all 59 tools.

Tool Name adjust_staking_position
Category Destructive
MCP Server Indigo MCP Server
Risk Level Critical

View all 59 tools →

Agents calling destructive-class tools like adjust_staking_position have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

adjust_staking_position is one of the critical-risk operations in Indigo. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the adjust_staking_position tool do? +

Adjust an existing INDY staking position (add or remove INDY). Returns an unsigned transaction (CBOR hex) for client-side signing.. It is categorised as a Destructive tool in the Indigo 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 adjust_staking_position? +

Add a rule in your Intercept YAML policy under the tools section for adjust_staking_position. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Indigo MCP server.

What risk level is adjust_staking_position? +

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

Yes. Add a rate_limit block to the adjust_staking_position rule in your Intercept 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 adjust_staking_position completely? +

Set action: deny in the Intercept policy for adjust_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 adjust_staking_position? +

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

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.