AI agents call get_moolah_history 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.
The tool retrieves historical data about a user's Moolah (likely a lending/borrowing protocol component on JustLend). Retrieval operations are classified as Read. The incomplete description ('Get a user') suggests it queries user history data without altering state. While the description is sparse, the action of 'get' combined with 'history' clearly indicates a read-only query.
From the tool's definition Tool name is 'get_moolah_history' and description states 'Get a user' — this is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get a user. 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 get_moolah_history: 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.
get_moolah_history 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 get_moolah_history 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 get_moolah_history. 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.
get_moolah_history 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 →