AI agents call check_jst_allowance_for_voting 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.
This is a read-only operation that retrieves the current allowance status of JST tokens for voting purposes. It performs no state mutations, creates no obligations, executes no arbitrary code, and cannot delete or move funds. The operation is informational and supports decision-making before other actions (like deposit).
From the tool's definition Tool checks approval status via 'check_jst_allowance_for_voting' - a query operation with no side effects. Description indicates it merely verifies whether JST has been approved, without modifying state.
Attacks that exploit this kind of access
Check if JST has been approved for the WJST voting contract. Must be approved before depositing JST to get votes. It is categorised as a Read tool in the Justlend MCP Server, which means it retrieves data without modifying state.
Register the Justlend MCP server in PolicyLayer and add a rule for check_jst_allowance_for_voting: 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.
check_jst_allowance_for_voting 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 check_jst_allowance_for_voting 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 check_jst_allowance_for_voting. 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.
check_jst_allowance_for_voting 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.
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 →