get_user_vote_status

Get a user

SERVERJustlend SOURCEjustlend/mcp-server-justlend

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/justlend-mcp-server-justlend/get-user-vote-status.md

WHAT IT DOES

What get_user_vote_status does on Justlend

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

RISK

Why get_user_vote_status is rated Low

This tool retrieves or queries user voting status data without side effects. It is a straightforward read operation that does not create, modify, delete, or execute any transactions. The blast radius of misuse is minimal—an agent could only access voting information about users, which does not impact funds or system integrity.

From the tool's definition Tool name 'get_user_vote_status' and description 'Get a user' indicate a retrieval operation that queries voting status information. No modification, execution, or financial transaction is performed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_user_vote_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Justlend, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_user_vote_status, this is the rule to start with:

get_user_vote_status Allowed

get_user_vote_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_user_vote_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Justlend, apply this rule, and every get_user_vote_status call is checked against it from then on.

FAQ

Questions about get_user_vote_status

What does the get_user_vote_status tool do? +

Get a user. 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 get_user_vote_status? +

Register the Justlend MCP server in PolicyLayer and add a rule for get_user_vote_status: 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 get_user_vote_status? +

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

Can I rate-limit get_user_vote_status? +

Yes. Add a rate_limit block to the get_user_vote_status 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 get_user_vote_status completely? +

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

get_user_vote_status 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.

KEEP EXPLORING

More on Justlend, and thousands of servers like it.

This server

All 104 Justlend tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →