upload_document_from_path · SharePoint MCP Server MCP

WHAT IT DOES

What upload_document_from_path does on SharePoint MCP Server

AI agents use upload_document_from_path 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 upload_document_from_path needs a policy

This tool creates or modifies data in SharePoint by uploading documents, making it a Write operation. Severity is medium because while it can introduce new content and consume storage, it is reversible (files can be deleted) and does not directly enable destructive operations, data theft, or financial transactions.

From the tool's definition Tool description explicitly states 'Upload a file from the local filesystem to SharePoint', which creates new data in SharePoint. The server description confirms 'document operations (upload, download, read, update, delete)'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_document_from_path Rate-limited

upload_document_from_path 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": {
    "upload_document_from_path": {
      "limits": [
        {
          "counter": "upload_document_from_path_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 upload_document_from_path

What does the upload_document_from_path tool do? +

Upload a file from the local filesystem to SharePoint. 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 upload_document_from_path? +

Register the SharePoint MCP Server MCP server in PolicyLayer and add a rule for upload_document_from_path: 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 upload_document_from_path? +

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

Can I rate-limit upload_document_from_path? +

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

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

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