Returns unbonding delegations for an address
AI agents call get-unbonding-delegations to retrieve information from Osmosis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries blockchain state to retrieve existing unbonding delegation information. It performs a read-only operation that returns data without modifying, deleting, or executing any transactions. While the broader server provides tools for financial transactions and destructive operations, this specific tool is a simple data lookup with minimal risk if misused by an AI agent.
From the tool's definition Tool name contains 'get-' prefix and description explicitly states 'Returns unbonding delegations for an address', indicating a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Returns unbonding delegations for an address. It is categorised as a Read tool in the Osmosis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for get-unbonding-delegations: 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 Osmosis MCP Server. Nothing to install.
get-unbonding-delegations 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-unbonding-delegations 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-unbonding-delegations. 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-unbonding-delegations is provided by the Osmosis MCP Server MCP server (myronkoch-dev/mcp-osmosis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →