get_strx_records

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-strx-records.md

WHAT IT DOES

What get_strx_records does on Justlend

AI agents call get_strx_records 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_strx_records is rated Low

This is a read-only operation that queries user data without side effects. Even though the description is minimal, the naming pattern and server context (portfolio management utilities) clearly indicate a retrieval function. Severity is low because reading user records on a public blockchain has limited blast radius.

From the tool's definition Tool name 'get_strx_records' and description 'Get a user' indicate data retrieval with no modification or execution. The context (JustLend DAO portfolio management) suggests this retrieves user STRX-related records or data from the blockchain.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_strx_records 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_strx_records, this is the rule to start with:

get_strx_records Allowed

get_strx_records 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_strx_records": {}
  }
}

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_strx_records call is checked against it from then on.

FAQ

Questions about get_strx_records

What does the get_strx_records 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_strx_records? +

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

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

Can I rate-limit get_strx_records? +

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

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

get_strx_records 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_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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