check_strx_withdrawal_eligibility

Check if user has TRX available to withdraw after sTRX unstaking unbonding period.

Server Justlend justlend/mcp-server-justlend
Category Read
Risk class Low
Parameters 00 required

What check_strx_withdrawal_eligibility does on Justlend

AI agents call check_strx_withdrawal_eligibility to retrieve information from Justlend without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_strx_withdrawal_eligibility needs a policy

This tool retrieves eligibility status information about a user's TRX withdrawal availability. It performs no state modifications, does not execute code or commands, does not delete data, and does not involve financial transactions. It is purely informational and carries minimal risk if misused by an AI agent, as it cannot cause harm beyond potentially exposing eligibility status information.

From the tool's definition Tool name and description indicate a query operation: 'Check if user has TRX available to withdraw'. The verb 'check' and the read-only nature of determining eligibility status confirm this is a data retrieval operation with no side effects.

Questions about check_strx_withdrawal_eligibility

What does the check_strx_withdrawal_eligibility tool do? +

Check if user has TRX available to withdraw after sTRX unstaking unbonding period. It is categorised as a Read tool in the Justlend MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_strx_withdrawal_eligibility? +

Register the Justlend MCP server in PolicyLayer and add a rule for check_strx_withdrawal_eligibility: 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 Justlend. Nothing to install.

What risk level is check_strx_withdrawal_eligibility? +

check_strx_withdrawal_eligibility is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_strx_withdrawal_eligibility? +

Yes. Add a rate_limit block to the check_strx_withdrawal_eligibility 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.

How do I block check_strx_withdrawal_eligibility completely? +

Set action: deny in the PolicyLayer policy for check_strx_withdrawal_eligibility. 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 check_strx_withdrawal_eligibility? +

check_strx_withdrawal_eligibility is provided by the Justlend MCP server (justlend/mcp-server-justlend). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.