inactivate_rentals
Inactivates a rental property and all associated units. Any associated property\
This record as markdown: /tools/wpm-mcp-server/inactivate-rentals.md
What inactivate_rentals does on Wpm Mcp Server
AI agents call inactivate_rentals to permanently remove resources in Wpm Mcp Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why inactivate_rentals is rated Critical
Inactivating a rental property and all associated units is a broad, potentially irreversible operation that affects multiple records simultaneously. The cascading effect on 'all associated units' and likely associated leases, tenants, and financial records makes this high severity.
From the tool's definition Inactivates a rental property and all associated units
Attacks that exploit this kind of access
The rule that runs inactivate_rentals 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 inactivate_rentals, this is the rule to start with:
inactivate_rentals is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Wpm Mcp Server, apply this rule, and every inactivate_rentals call is checked against it from then on.
Questions about inactivate_rentals
Inactivates a rental property and all associated units. Any associated property\. It is categorised as a Destructive tool in the Wpm Mcp Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for inactivate_rentals: 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.
inactivate_rentals is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the inactivate_rentals 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 inactivate_rentals. 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.
inactivate_rentals 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.
Across the catalogue