Download a document from SharePoint to the local filesystem
AI agents call download_document to retrieve information from SharePoint MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Downloading a document is a read operation that retrieves data without side effects. While it copies data to the local filesystem, it does not modify, delete, or create resources in SharePoint itself. The confidentiality risk depends on document sensitivity, but the tool's functional impact is limited to data retrieval.
From the tool's definition Tool description states 'Download a document from SharePoint to the local filesystem' — a retrieval operation with no modification or deletion of source data.
Attacks that exploit this kind of access
Download a document from SharePoint to the local filesystem. It is categorised as a Read tool in the SharePoint MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SharePoint MCP Server MCP server in PolicyLayer and add a rule for download_document: 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.
download_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the download_document 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 download_document. 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.
download_document 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.
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 →