Analyze nearby rental market conditions and pricing.
AI agents call market_rent_analysis 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.
The tool retrieves and analyzes existing market data to support decision-making. It queries and examines rental market conditions without creating, modifying, deleting, or executing any operations that would have side effects or financial impact. This is consistent with the Read category for data retrieval and analysis tools.
From the tool's definition Tool description states 'Analyze nearby rental market conditions and pricing' — a data retrieval and analysis operation with no modification, deletion, or execution of external processes.
Attacks that exploit this kind of access
Analyze nearby rental market conditions and pricing. 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 market_rent_analysis: 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.
market_rent_analysis 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 market_rent_analysis 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 market_rent_analysis. 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.
market_rent_analysis 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 →