add_site
Add a Moodle site to this server, kept for later sessions: its URL (any page of it works) and, optionally, a short name (letters, digits, dots, hyphens; its host by default). Without url, the person is asked for both in their app, where the client can ask them (MCP elicitation); else ask them you...
This record as markdown: /tools/falkenslab-moodle-mcp/add-site.md
What add_site does on Moodle
AI agents use add_site 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | The site's URL, or any page of it; without it, the person is asked in their app when it can |
name | string | — | A short name for it; its host by default |
Parameters from the server's own tool schema.
Why add_site is rated Medium
An AI agent can call add_site faster than any human can review: one bad instruction and it creates or modifies resources in Moodle by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs add_site safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Moodle, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_site, this is the rule to start with:
add_site stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Moodle, apply this rule, and every add_site call is checked against it from then on.
Questions about add_site
Add a Moodle site to this server, kept for later sessions: its URL (any page of it works) and, optionally, a short name (letters, digits, dots, hyphens; its host by default). Without url, the person is asked for both in their app, where the client can ask them (MCP elicitation); else ask them yourself. Two accounts on one site are two sites: add the second with a name of its own. It doesn't become active: switch to it with use_site, and log in there when a tool asks. Only when the person asks for another site. 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.
add_site accepts 2 parameters: url, name. The full parameter table on this page comes from the server's own tool schema.
Register the Moodle MCP server in PolicyLayer and add a rule for add_site: 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.
add_site 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 add_site 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 add_site. 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.
add_site is provided by the Moodle MCP server (@falkenslab/moodle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Moodle, and thousands of servers like it.
This server
Across the catalogue