get_staking_positions
Get all open INDY staking positions
This record as markdown: /tools/indigoprotocol-indigo-mcp/get-staking-positions.md
What get_staking_positions does on Indigo Protocol MCP
AI agents call get_staking_positions to retrieve information from Indigo Protocol MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_staking_positions is rated Low
This tool retrieves data about staking positions without any side effects. It does not create, modify, delete, or execute operations; it only reads and returns information. This is a straightforward Read operation with minimal security risk — an agent misusing it can only access information that should be available to querying users.
From the tool's definition Tool name is 'get_staking_positions' and description states 'Get all open INDY staking positions' — a retrieval/query operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
The rule that runs get_staking_positions 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 get_staking_positions, this is the rule to start with:
get_staking_positions is read-only, so it stays allowed. 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 get_staking_positions call is checked against it from then on.
Questions about get_staking_positions
Get all open INDY staking positions. It is categorised as a Read tool in the Indigo Protocol MCP MCP Server, which means it retrieves data without modifying state.
Register the Indigo Protocol MCP server in PolicyLayer and add a rule for get_staking_positions: 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.
get_staking_positions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_staking_positions 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 get_staking_positions. 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.
get_staking_positions 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