Undelegate Superfluid staked tokens
AI agents invoke superfluid-undelegate to trigger actions in Osmosis MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Undelegating superfluid staked tokens is a blockchain transaction execution that changes the staking state of tokens. While it can be reversed by re-delegating, undelegation typically initiates an unbonding period and has significant financial implications (loss of staking rewards, exposure to price risk during unbonding).
From the tool's definition 'Undelegate Superfluid staked tokens' — triggers a blockchain transaction that removes staking delegation from superfluid staked positions
Attacks that exploit this kind of access
Undelegate Superfluid staked tokens. It is categorised as a Execute tool in the Osmosis MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for superfluid-undelegate: 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.
superfluid-undelegate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the superfluid-undelegate 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 superfluid-undelegate. 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.
superfluid-undelegate 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 →