Check whether a person is likely eligible for a specific lender
AI agents call check_eligibility 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 queries eligibility criteria against a borrower profile to determine compatibility with a lender. It performs no data modification, deletion, financial transactions, or code execution. It is a straightforward read operation that returns information to inform decision-making, with no side effects or irreversible actions.
From the tool's definition Tool description states 'Check whether a person is likely eligible' - this is a lookup/query operation that retrieves eligibility information. The server description emphasizes querying lenders and checking eligibility without modifying data.
Attacks that exploit this kind of access
Check whether a person is likely eligible for a specific lender. 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 check_eligibility: 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.
check_eligibility 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_eligibility 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_eligibility. 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_eligibility 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 →