Compare two or more lenders side by side. Provides a comparison table of key metrics.
AI agents call compare_lenders to retrieve information from Lenderwiki without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents information about lenders in a structured comparison format. It has no side effects—it does not create, modify, delete, or execute operations. The user can safely call it multiple times with different lender combinations and receive the same underlying data presented in different ways. No financial transactions, code execution, or data modification occurs.
From the tool's definition Tool name 'compare_lenders' and description 'Compare two or more lenders side by side. Provides a comparison table of key metrics.' indicate data retrieval and presentation only.
Attacks that exploit this kind of access
Compare two or more lenders side by side. Provides a comparison table of key metrics. It is categorised as a Read tool in the Lenderwiki MCP Server, which means it retrieves data without modifying state.
Register the Lenderwiki MCP server in PolicyLayer and add a rule for compare_lenders: 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 Lenderwiki. Nothing to install.
compare_lenders 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 compare_lenders 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 compare_lenders. 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.
compare_lenders is provided by the Lenderwiki MCP server (lenderwiki/mcp-server). 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 →