Deletes a specific file from a task history record. The file will be permanently deleted from the Buildium platform an can not be recovered.\r\n \r\n\r\nThis endpoint can be used for any task type - contact requests, rental owner requests, resident requests or to do\
AI agents call delete_history_tasks_files 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 and irreversibly removes file data with no recovery mechanism. It meets the Destructive category definition as it deletes data that cannot be undone. The high severity reflects the permanent loss of potentially important task history records in a property management system, which could affect compliance, auditing, or operational records.
From the tool's definition Tool description explicitly states 'Deletes a specific file from a task history record. The file will be permanently deleted from the Buildium platform an can not be recovered.' The use of 'delete', 'permanently deleted', and 'can not be recovered' directly…
Attacks that exploit this kind of access
Deletes a specific file from a task history record. The file will be permanently deleted from the Buildium platform an can not be recovered.\r\n \r\n\r\nThis endpoint can be used for any task type - contact requests, rental owner requests, resident requests or to do\. 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_history_tasks_files: 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_history_tasks_files 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_history_tasks_files 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_history_tasks_files. 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_history_tasks_files 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 →