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.
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.
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.
Documented attack patterns abuse exactly the kind of access powerpoint_upload_presentation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for powerpoint_upload_presentation:
{
"version": "1",
"default": "deny",
"tools": {
"powerpoint_upload_presentation": {
"limits": [
{
"counter": "powerpoint_upload_presentation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.