Updates a rent schedule.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=
AI agents use update_leases_rent to create or update resources in Wpm Mcp Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wpm Mcp Server environment.
This tool modifies rent schedule records, which are reversible changes to existing data structures. While it operates in a financial domain (leases/rent management), it updates rather than moves money directly, nor does it irreversibly delete data. It is categorized as Write rather than Financial because the core action is data modification, not a financial transaction.
From the tool's definition Tool name 'update_leases_rent' and description 'Updates a rent schedule' indicates modification of existing lease/rent data.
Attacks that exploit this kind of access
Updates a rent schedule.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=. It is categorised as a Write tool in the Wpm Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for update_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.
update_leases_rent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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.
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 →