get-drive-delta
Track changes in a driveItem and its children over time. Your app begins by calling delta without any parameters. The service starts enumerating the drive's hierarchy, returning pages of items and either an @odata.nextLink or an @odata.deltaLink, as described below. Your app should continue calli...
This record as markdown: /tools/jo3zik-ms-365-mcp-server/get-drive-delta.md
What get-drive-delta does on Ms 365
AI agents call get-drive-delta to retrieve information from Ms 365 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
top | number | — | Page size (Graph $top). Start small (e.g. 5–15) so responses fit the model context; raise only if needed. Use $select to return fewer fields per item. For more |
skip | number | — | Items to skip for pagination. Not supported with $search. |
count | boolean | — | Set true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains(). |
expand | array | — | Navigation properties to inline, e.g. attachments on a message or event. Only navigation properties can be expanded: expanding a non-navigation property such as |
filter | string | — | OData filter expression. Add $count=true for advanced filters (flag/flagStatus, contains()). Cannot combine with $search. |
search | string | — | KQL search query — wrap value in double quotes. Cannot combine with $filter. |
select | string | — | Comma-separated fields to return, e.g. id,subject,from,receivedDateTime |
driveId | string | Yes | Value for the 'driveId' path segment. Pass it under the name 'driveId', not as 'id'. Use the 'id' field of the drive object as returned by Microsoft Graph. |
orderby | string | — | Sort expression, e.g. receivedDateTime desc |
driveItemId | string | Yes | Value for the 'driveItemId' path segment. Pass it under the name 'driveItemId', not as 'id'. Use the 'id' field of the drive item object as returned by Microsof |
fetchAllPages | boolean | — | Follow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a sma |
includeHeaders | boolean | — | Include response headers (including ETag) in the response metadata |
Parameters from the server's own tool schema.
Why get-drive-delta is rated Low
Even though get-drive-delta only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (13 properties) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs get-drive-delta safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ms 365, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-drive-delta, this is the rule to start with:
get-drive-delta 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 Ms 365, apply this rule, and every get-drive-delta call is checked against it from then on.
Questions about get-drive-delta
Track changes in a driveItem and its children over time. Your app begins by calling delta without any parameters. The service starts enumerating the drive's hierarchy, returning pages of items and either an @odata.nextLink or an @odata.deltaLink, as described below. Your app should continue calling with the @odata.nextLink until you no longer see an @odata.nextLink returned, or you see a response with an empty set of changes. After you have finished receiving all the changes, you may apply them to your local state. To check for changes in the future, call delta again with the @odata.deltaLink from the previous response. Deleted items are returned with the deleted facet. Items with this property set should be removed from your local state. 💡 TIP: Tracks changes to a driveItem and its children over time. Returns a collection of driveItems that have been created, modified, or deleted. Use get-drive-root-item first to get the root driveItem-id, then pass it here. Supports $select and delta tokens for incremental sync via @odata.deltaLink. It is categorised as a Read tool in the Ms 365 MCP Server, which means it retrieves data without modifying state.
get-drive-delta accepts 12 parameters: top, skip, count, expand, filter, search, select, driveId, orderby, driveItemId, fetchAllPages, includeHeaders. Required: driveId, driveItemId. The full parameter table on this page comes from the server's own tool schema.
Register the Ms 365 MCP server in PolicyLayer and add a rule for get-drive-delta: 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 Ms 365. Nothing to install.
get-drive-delta 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-drive-delta 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-drive-delta. 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-drive-delta is provided by the Ms 365 MCP server (@jo3zik/ms-365-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ms 365, and thousands of servers like it.
This server
Across the catalogue