Find qualified prospects based on income and credit requirements.
AI agents call qualified_prospects to retrieve information from Tenant Leasing Analytics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters prospect data based on specified criteria (income and credit requirements) without modifying, deleting, or executing external operations. It performs a straightforward search query against tenant prospect data, characteristic of Read category tools. No side effects or data changes result from its use.
From the tool's definition Tool name 'qualified_prospects' with description 'Find qualified prospects' indicates a search/query operation.
Attacks that exploit this kind of access
Find qualified prospects based on income and credit requirements. It is categorised as a Read tool in the Tenant Leasing Analytics MCP Server, which means it retrieves data without modifying state.
Register the Tenant Leasing Analytics MCP server in PolicyLayer and add a rule for qualified_prospects: 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 Tenant Leasing Analytics. Nothing to install.
qualified_prospects 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 qualified_prospects 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 qualified_prospects. 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.
qualified_prospects is provided by the Tenant Leasing Analytics MCP server (kkamalvanshi/tenant-leasing-mcp). 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 →