get_document_by_path
A read tool on the Sharepoint MCP server.
This record as markdown: /tools/demodorigatsuo-sharepoint-mcp/get-document-by-path.md
What get_document_by_path does on Sharepoint
AI agents call get_document_by_path to retrieve information from Sharepoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_document_by_path is rated Low
This tool retrieves a document from SharePoint by its path, a read-only operation with no side effects. It is classified as Read rather than a higher category. Severity is medium rather than low because an AI agent could use path traversal or enumerate documents across the organization to access sensitive information, and SharePoint often contains confidential business data, intellectual property, or personal…
From the tool's definition Tool name 'get_document_by_path' indicates retrieval of document content by file path; sibling tools include 'download_file' and 'get_document_content' which are clearly read operations, and 'get_item_metadata' and 'get_list_items' which query data.
Attacks that exploit this kind of access
The rule that runs get_document_by_path safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sharepoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_document_by_path, this is the rule to start with:
get_document_by_path is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sharepoint, apply this rule, and every get_document_by_path call is checked against it from then on.
Questions about get_document_by_path
get_document_by_path is a read tool on the Sharepoint MCP server. It is categorised as a Read tool in the Sharepoint MCP Server, which means it retrieves data without modifying state.
Register the Sharepoint MCP server in PolicyLayer and add a rule for get_document_by_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. Nothing to install.
get_document_by_path 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 get_document_by_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.
Set action: deny in the PolicyLayer policy for get_document_by_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.
get_document_by_path is provided by the Sharepoint MCP server (demodorigatsuo/sharepoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sharepoint, and thousands of servers like it.
This server
Across the catalogue