AI agents use ocultar_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 modifies course content visibility settings but does not delete data or perform irreversible operations. Hiding a section is reversible (can be unhidden), making it a Write operation rather than Destructive. The blast radius is medium because incorrect use could inadvertently conceal course materials from students, disrupting their learning experience, but the action is recoverable.
From the tool's definition Tool name 'ocultar_seccion' means 'hide section'; description states it hides 'a course section (and its modules) from students'. This is a state modification (visibility change) that is reversible by unhiding.
Attacks that exploit this kind of access
Hide a course section (and its modules) from students. Uses local_wsmanagesections. 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 ocultar_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.
ocultar_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 ocultar_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 ocultar_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.
ocultar_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 →