Delete events from a longitudinal REDCap project.
AI agents call delete_events to permanently remove resources in Redcap — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes events from a REDCap project, which cannot be undone. Events are structural components of longitudinal studies that organize timepoints and data collection instances. Deleting events would cause irreversible data loss or project structure corruption.
From the tool's definition Tool name is 'delete_events' and description states 'Delete events from a longitudinal REDCap project.' The verb 'delete' combined with the irreversible nature of removing events from a research data management system indicates a destructive operation.
Attacks that exploit this kind of access
Delete events from a longitudinal REDCap project. It is categorised as a Destructive tool in the Redcap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redcap MCP server in PolicyLayer and add a rule for delete_events: 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 Redcap. Nothing to install.
delete_events 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_events 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_events. 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_events is provided by the Redcap MCP server (msicilia/mcp-server-redcap). 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 →