AI agents use crear_seccion 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 course content structures reversibly within Moodle. While it modifies the course layout and could affect the learning environment if misused at scale, the action is reversible (sections can be deleted or reorganized). It does not execute arbitrary code, delete data irreversibly, or involve financial transactions.
From the tool's definition Tool name 'crear_seccion' (create section) and description 'Create a new section in a course' indicate data creation. The tool creates a new pedagogical structure (course section) with configurable properties (name, summary, position, visibility).
Attacks that exploit this kind of access
Create a new section in a course with a given name, summary, position and initial visibility. Requires the. 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_seccion: 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_seccion 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_seccion 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_seccion. 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_seccion 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 →