This record as markdown: /tools/launch-on-basis-mcp-ts/unstake-stasis.md
What unstake_stasis does on Basis MCP Server
AI agents call unstake_stasis to retrieve information from Basis MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why unstake_stasis is rated Low
Even though unstake_stasis only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs unstake_stasis safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unstake_stasis, this is the rule to start with:
unstake_stasis 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 Basis MCP Server, apply this rule, and every unstake_stasis call is checked against it from then on.
Questions about unstake_stasis
Unwrap/sell staked STASIS. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for unstake_stasis: 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 Basis MCP Server. Nothing to install.
unstake_stasis 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 unstake_stasis 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 unstake_stasis. 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.
unstake_stasis is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Basis MCP Server, and thousands of servers like it.
This server
Across the catalogue