AI agents call listar_eventos_calendario to retrieve information from Moodle without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation that retrieves calendar event data without side effects. It accepts filtering parameters (courses, groups, categories, timestart, timeend) but only returns information. There is no capability to create, modify, delete, or execute operations.
From the tool's definition Tool name 'listar_eventos_calendario' (list calendar events) and description 'List calendar events by courses/groups/categories, optionally filtered by a timestart/timeend range' indicate a retrieval operation with optional filtering parameters.
Attacks that exploit this kind of access
List calendar events by courses/groups/categories, optionally filtered by a timestart/timeend range. It is categorised as a Read tool in the Moodle MCP Server, which means it retrieves data without modifying state.
Register the Moodle MCP server in PolicyLayer and add a rule for listar_eventos_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.
listar_eventos_calendario is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listar_eventos_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 listar_eventos_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.
listar_eventos_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 →