powerpoint_upload_presentation
Get the upload URL for updating an existing PowerPoint file. Binary file upload is not practical via MCP tool calls; this returns the endpoint and instructions for direct Graph API upload.
This record as markdown: /tools/sagemcp-sagemcp/powerpoint-upload-presentation.md
What powerpoint_upload_presentation does on Sage MCP
AI agents use powerpoint_upload_presentation to create or update resources in Sage MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sage MCP environment.
Why powerpoint_upload_presentation is rated Medium
This tool enables creation or modification of PowerPoint documents by returning an upload URL and instructions for updating files via the Microsoft Graph API. While the actual binary upload occurs outside MCP, the tool itself facilitates a reversible write operation (uploading/updating a file). It does not delete data (would be Destructive) or execute arbitrary code (would be Execute).
From the tool's definition Tool description explicitly states it is for 'updating an existing PowerPoint file' and provides 'endpoint and instructions for direct Graph API upload.' The word 'updating' and 'upload' indicate modification of data.
Attacks that exploit this kind of access
The rule that runs powerpoint_upload_presentation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For powerpoint_upload_presentation, this is the rule to start with:
powerpoint_upload_presentation 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every powerpoint_upload_presentation call is checked against it from then on.
Questions about powerpoint_upload_presentation
Get the upload URL for updating an existing PowerPoint file. Binary file upload is not practical via MCP tool calls; this returns the endpoint and instructions for direct Graph API upload. It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sage MCP server in PolicyLayer and add a rule for powerpoint_upload_presentation: 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 Sage MCP. Nothing to install.
powerpoint_upload_presentation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the powerpoint_upload_presentation 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 powerpoint_upload_presentation. 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.
powerpoint_upload_presentation is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue