use_site

SERVERMoodle SOURCE@falkenslab/moodle-mcp

Medium RISK CLASS

Category Write

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/falkenslab-moodle-mcp/use-site.md

WHAT IT DOES

What use_site does on Moodle

AI agents use use_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
`name`	string	Yes	The site's name, as list_sites gives it

Parameters from the server's own tool schema.

RISK

Why use_site is rated Medium

An AI agent can call use_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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs use_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 use_site, this is the rule to start with:

use_site Rate-limited

use_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "use_site": {
      "limits": [
        {
          "counter": "use_site_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Moodle, apply this rule, and every use_site call is checked against it from then on.

FAQ

Questions about use_site

What does the use_site tool do? +

Make another known site the active one, by name (list_sites): every other tool works on it from now on. The previous site's browser closes and keeps its session; if the new one has none, the next tool asks to log in. Tell the person which site you're now working on. Lasts for this session. 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.

What parameters does use_site accept? +

use_site accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on use_site? +

Register the Moodle MCP server in PolicyLayer and add a rule for use_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.

What risk level is use_site? +

use_site is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit use_site? +

Yes. Add a rate_limit block to the use_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.

How do I block use_site completely? +

Set action: deny in the PolicyLayer policy for use_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.

What MCP server provides use_site? +

use_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.

KEEP EXPLORING

More on Moodle, and thousands of servers like it.

This server

All 233 Moodle tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →