generate_leasing_email · Tenant Leasing Analytics MCP

WHAT IT DOES

What generate_leasing_email does on Tenant Leasing Analytics

AI agents use generate_leasing_email to create or update resources in Tenant Leasing Analytics — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tenant Leasing Analytics environment.

WHY IT NEEDS A POLICY

Why generate_leasing_email needs a policy

Generating leasing emails creates new data (email messages) that would typically be sent to prospects, constituting a Write operation with potential to reach external parties. Severity is medium because misuse could send unwanted communications or inappropriate messages to tenants, but lacks the irreversibility of Destructive or financial obligations of Financial category.

From the tool's definition Tool name 'generate_leasing_email' combined with server context describing 'automated generation of leasing emails' indicates this tool creates email content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_leasing_email Rate-limited

generate_leasing_email stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_leasing_email": {
      "limits": [
        {
          "counter": "generate_leasing_email_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tenant Leasing Analytics, so you can run agents against it safely.

FAQ

Questions about generate_leasing_email

What does the generate_leasing_email tool do? +

generate_leasing_email. It is categorised as a Write tool in the Tenant Leasing Analytics MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_leasing_email? +

Register the Tenant Leasing Analytics MCP server in PolicyLayer and add a rule for generate_leasing_email: 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.

What risk level is generate_leasing_email? +

generate_leasing_email is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_leasing_email? +

Yes. Add a rate_limit block to the generate_leasing_email 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.

How do I block generate_leasing_email completely? +

Set action: deny in the PolicyLayer policy for generate_leasing_email. 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.

What MCP server provides generate_leasing_email? +

generate_leasing_email 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.