AI agents use reordenar_secciones 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 modifies existing data (section ordering) within Moodle but does not delete, create new sections, or execute arbitrary code. Reordering is a reversible operation—sections can be reordered again to restore prior state. It falls into the Write category.
From the tool's definition Tool description states it 'Reorder sections in a course' and 'applies them in one batched update_sections call.' The verb 'reorder' modifies the structure/metadata of course sections reversibly.
Attacks that exploit this kind of access
Reorder sections in a course. Accepts an array of {section_id, position} and applies them in one batched update_sections call. 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 reordenar_secciones: 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.
reordenar_secciones 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 reordenar_secciones 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 reordenar_secciones. 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.
reordenar_secciones 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 →