Analyze a parsed rent roll for investment risks. Feed the output from analyze_rent_roll directly into this tool. Returns: rollover risk, tenant concentration, credit risk, and actionable recommendations.
AI agents call flag_lease_risks to retrieve information from CRE Intelligence MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
rent_roll_json | string | Yes | JSON string from the analyze_rent_roll tool output |
Parameters from the server's own tool schema.
This tool performs analytical computation on already-parsed rent roll data and returns insights. It does not create, modify, delete, or execute external operations. The output is informational analysis to support decision-making, with no irreversible effects or state changes. Classification as Read is appropriate for query/analysis tools that consume and report on data without side effects.
From the tool's definition Tool analyzes and returns risk assessments (rollover risk, tenant concentration, credit risk, recommendations) from parsed rent roll data.
Attacks that exploit this kind of access
Analyze a parsed rent roll for investment risks. Feed the output from analyze_rent_roll directly into this tool. Returns: rollover risk, tenant concentration, credit risk, and actionable recommendations. It is categorised as a Read tool in the CRE Intelligence MCP MCP Server, which means it retrieves data without modifying state.
flag_lease_risks accepts 1 parameter: rent_roll_json. Required: rent_roll_json. The full parameter table on this page comes from the server's own tool schema.
Register the CRE Intelligence MCP server in PolicyLayer and add a rule for flag_lease_risks: 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 CRE Intelligence MCP. Nothing to install.
flag_lease_risks 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 flag_lease_risks 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 flag_lease_risks. 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.
flag_lease_risks is provided by the CRE Intelligence MCP server (Zwondra/cre-intelligence-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 →