Delete a record
AI agents call delete_record to permanently remove resources in Prowpt MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a record is an irreversible operation that permanently removes data. Even though it operates on a single record rather than bulk data, it cannot be undone and represents a destructive action. Given the context of a web app management platform where records likely contain user data or application content, this poses a significant risk if invoked incorrectly by an AI agent.
From the tool's definition Tool name is 'delete_record' with description 'Delete a record'. The verb 'delete' combined with the action of removing a record indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a record. It is categorised as a Destructive tool in the Prowpt MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Prowpt MCP Server MCP server in PolicyLayer and add a rule for delete_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 Prowpt MCP Server. Nothing to install.
delete_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_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_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_record is provided by the Prowpt MCP Server MCP server (prowptai/prowpt-mcp-server). 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 →