This record as markdown: /tools/app-businys-mcp-server/delete-personal-record.md
What delete_personal_record does on Businys
AI agents call delete_personal_record to permanently remove resources in Businys, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_personal_record is rated Critical
This tool permanently removes data without the ability to undo the action, fitting the Destructive category. Severity is high because an AI agent could inadvertently delete important fitness/athletic records that hold sentimental or motivational value to users, and recovery would require backup restoration or manual re-entry. The confidence is high due to clear evidence in both name and description.
From the tool's definition Tool name 'delete_personal_record' explicitly performs a delete operation. Description confirms 'Delete a personal record.' The action is irreversible — deleted personal records cannot be recovered.
Attacks that exploit this kind of access
The rule that runs delete_personal_record safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_personal_record, this is the rule to start with:
delete_personal_record 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 Businys, apply this rule, and every delete_personal_record call is checked against it from then on.
Questions about delete_personal_record
Delete a personal record. It is categorised as a Destructive tool in the Businys MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Businys MCP server in PolicyLayer and add a rule for delete_personal_record: 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 Businys. Nothing to install.
delete_personal_record 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_personal_record 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_personal_record. 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_personal_record is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
Across the catalogue