Deleting a listing will immediately remove it from your Buildium public website. The listing will also be removed\r\nfrom any syndicated sites within 24-48 hours.\r\n\r\nListings manually created on craigslist using the Buildium\r\nguided tool will not be removed. The listing must be removed usin...
AI agents call delete_all_units_rentals_listing 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.
This tool permanently removes rental listings from the Buildium public website and syndicated platforms. The deletion is immediate and cannot be undone, making it destructive. While not financial in nature, it causes significant business harm by removing income-generating listings. The 'delete_all' prefix and immediate removal action classify this as Destructive rather than Write.
From the tool's definition Tool name includes 'delete_all' and description states 'Deleting a listing will immediately remove it from your Buildium public website' with syndicated removal within 24-48 hours. This is irreversible removal of rental listings.
Attacks that exploit this kind of access
Deleting a listing will immediately remove it from your Buildium public website. The listing will also be removed\r\nfrom any syndicated sites within 24-48 hours.\r\n\r\nListings manually created on craigslist using the Buildium\r\nguided tool will not be removed. The listing must be removed using craigslist\. 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 delete_all_units_rentals_listing: 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.
delete_all_units_rentals_listing 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 delete_all_units_rentals_listing 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 delete_all_units_rentals_listing. 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.
delete_all_units_rentals_listing 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 →