set_site · SharePoint MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_site does on SharePoint MCP Server

AI agents use set_site to create or update resources in SharePoint MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SharePoint MCP Server environment.

WHY IT NEEDS A POLICY

Why set_site needs a policy

This tool modifies configuration state by setting the active site URL for subsequent operations. While it does not create, delete, or query data directly, it is a Write operation as it changes the agent's working context. Severity is low because the operation is reversible (can be reset to a different site) and has no direct side effects on SharePoint data itself; it merely directs where other tools will operate.

From the tool's definition Tool name 'set_site' and description indicate it sets or modifies configuration state (the active SharePoint site URL). The description states it 'must be called before any other tool if SITE_URL is not set in .env', indicating it configures runtime state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_site Rate-limited

set_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": {
    "set_site": {
      "limits": [
        {
          "counter": "set_site_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SharePoint MCP Server, so you can run agents against it safely.

FAQ

Questions about set_site

What does the set_site tool do? +

Set the SharePoint site URL to work with. Must be called before any other tool if SITE_URL is not set in .env. It is categorised as a Write tool in the SharePoint MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_site? +

Register the SharePoint MCP Server MCP server in PolicyLayer and add a rule for set_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 SharePoint MCP Server. Nothing to install.

What risk level is set_site? +

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

Can I rate-limit set_site? +

Yes. Add a rate_limit block to the set_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 set_site completely? +

Set action: deny in the PolicyLayer policy for set_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 set_site? +

set_site is provided by the SharePoint MCP Server MCP server (lukassevcik/sharepoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.