AI agents use confirmar_preview 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 or modifies data reversibly by changing visibility settings of course sections and their modules. While it affects student access to content, the operation is reversible (sections can be hidden again), placing it in the Write category rather than Execute or Destructive.
From the tool's definition Tool description states it makes a previewed section 'visible to students' and 'propagates visibility to all modules inside the section.' This is a modification operation that changes the state of educational content from hidden/preview status to…
Attacks that exploit this kind of access
Make a previewed section visible to students. Propagates visibility to all modules inside the section. Idempotent. 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 confirmar_preview: 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.
confirmar_preview 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 confirmar_preview 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 confirmar_preview. 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.
confirmar_preview 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 →