AI agents use crear_evento_calendario 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.
This tool creates new calendar events in Moodle, which is a reversible write operation. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), involves no financial transactions (not Financial), and has no read-only characteristics (not Read).
From the tool's definition Tool creates a calendar event with 'Create' explicitly in the name and description stating 'Create a calendar event.' It accepts parameters for event configuration including repeat_count for recurrences, and returns the created event id and metadata.
Attacks that exploit this kind of access
Create a calendar event. Default eventtype=course. Set repeat_count>0 to create weekly recurrences. Returns the created event id and metadata. 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 crear_evento_calendario: 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.
crear_evento_calendario 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 crear_evento_calendario 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 crear_evento_calendario. 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.
crear_evento_calendario 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 →