Delete one or more calendar events. Set delete_repeats=true to remove repeat instances as well.
AI agents call eliminar_evento to permanently remove resources in Moodle — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (calendar events) that cannot be restored through normal means. Deletion is irreversible and destructive, making it the most severe category. The high severity reflects that an AI agent could accidentally or maliciously delete important course events, affecting students and instructors.
From the tool's definition The tool explicitly uses the word 'Delete' and performs irreversible removal of calendar events from Moodle. The parameter 'delete_repeats=true' indicates it can cascade delete multiple instances.
Attacks that exploit this kind of access
Delete one or more calendar events. Set delete_repeats=true to remove repeat instances as well. It is categorised as a Destructive tool in the Moodle MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Moodle MCP server in PolicyLayer and add a rule for eliminar_evento: 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 Moodle. Nothing to install.
eliminar_evento 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 eliminar_evento 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 eliminar_evento. 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.
eliminar_evento is provided by the Moodle MCP server (marcosnahuel/moodle-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 →