get_by_lease_leases_rent
The rent schedule provides details (dollar amount, day of the month, etc) of the recurring charges that are applied to the lease ledger each rent cycle. A lease may have more than one rent schedule associated with it if the rent terms change within the duration of the lease.\r\n \r\n\r\n<h4>Requi...
This record as markdown: /tools/wpm-mcp-server/get-by-lease-leases-rent.md
What get_by_lease_leases_rent does on Wpm Mcp Server
AI agents call get_by_lease_leases_rent to retrieve information from Wpm Mcp Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_by_lease_leases_rent is rated Low
This tool retrieves rent schedule details from a lease record. It queries and returns information about recurring charges without creating, modifying, deleting, or executing any operations. This is a read-only data retrieval operation with minimal risk if misused by an AI agent—it can only expose financial information, not move money or alter records.
From the tool's definition Tool name 'get_by_lease_leases_rent' uses 'get' verb indicating retrieval. Description states it 'provides details (dollar amount, day of the month, etc) of the recurring charges' which is a query operation retrieving lease rent schedule information.
Attacks that exploit this kind of access
The rule that runs get_by_lease_leases_rent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wpm Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_by_lease_leases_rent, this is the rule to start with:
get_by_lease_leases_rent is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Wpm Mcp Server, apply this rule, and every get_by_lease_leases_rent call is checked against it from then on.
Questions about get_by_lease_leases_rent
The rent schedule provides details (dollar amount, day of the month, etc) of the recurring charges that are applied to the lease ledger each rent cycle. A lease may have more than one rent schedule associated with it if the rent terms change within the duration of the lease.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=. It is categorised as a Read tool in the Wpm Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for get_by_lease_leases_rent: 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 Wpm Mcp Server. Nothing to install.
get_by_lease_leases_rent 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 get_by_lease_leases_rent 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 get_by_lease_leases_rent. 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.
get_by_lease_leases_rent is provided by the Wpm Mcp Server MCP server (wpm-mcp-server-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wpm Mcp Server, and thousands of servers like it.
This server
Across the catalogue