AI agents use actualizar_evento to create or update resources in Moodle — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Moodle environment.
The tool modifies an existing calendar event by changing its scheduled time. This is a reversible write operation (the event can be rescheduled again). The note about needing to delete+recreate for other fields implies this tool only updates timestart, not deleting anything itself. Severity is medium because misconfigured event times could disrupt course scheduling for many students.
From the tool's definition Reschedule a calendar event to a new timestart
Attacks that exploit this kind of access
Reschedule a calendar event to a new timestart. To change name/description/location, delete + re-create (Moodle WS does not expose full event update). It is categorised as a Write tool in the Moodle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Moodle MCP server in PolicyLayer and add a rule for actualizar_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.
actualizar_evento is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the actualizar_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 actualizar_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.
actualizar_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 →