AI agents use publicar_ficha_clase 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 pedagogical content (sections and modules) within Moodle courses. Publishing a lesson plan with components is a Write operation—it alters course structure reversibly. While it affects educational content, it is not Destructive (no deletion), Execute (no arbitrary code), or Financial.
From the tool's definition The tool 'publicar_ficha_clase' publishes content and creates/updates Moodle sections with modules. The description explicitly states it 'updates in place, never duplicates' and is 'Idempotent', indicating reversible modifications to course structure and…
Attacks that exploit this kind of access
Publish a FichaClase markdown file as a Moodle section with component modules. Idempotent: republishing the same Ficha updates in place, never duplicates. Default modo is. 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 publicar_ficha_clase: 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.
publicar_ficha_clase 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 publicar_ficha_clase 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 publicar_ficha_clase. 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.
publicar_ficha_clase 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 →