get-planner-task
Retrieve the properties and relationships of plannerTask object. 💡 TIP: Response includes @odata.etag — save it, required as If-Match header for update-planner-task. Use includeHeaders=true to capture it.
This record as markdown: /tools/jo3zik-ms-365-mcp-server/get-planner-task.md
What get-planner-task does on Ms 365
AI agents call get-planner-task 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 |
|---|---|---|---|
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 |
select | string | — | Comma-separated fields to return, e.g. id,subject,from,receivedDateTime |
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 |
plannerTaskId | string | Yes | Value for the 'plannerTaskId' path segment. Pass it under the name 'plannerTaskId', not as 'id'. Use the 'id' field of the planner task object as returned by Mi |
includeHeaders | boolean | — | Include response headers (including ETag) in the response metadata |
excludeResponse | boolean | — | Exclude the full response body and only return success or failure indication |
Parameters from the server's own tool schema.
Why get-planner-task is rated Low
Even though get-planner-task 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.
Attacks that exploit this kind of access
The rule that runs get-planner-task 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-planner-task, this is the rule to start with:
get-planner-task 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-planner-task call is checked against it from then on.
Questions about get-planner-task
Retrieve the properties and relationships of plannerTask object. 💡 TIP: Response includes @odata.etag — save it, required as If-Match header for update-planner-task. Use includeHeaders=true to capture it. It is categorised as a Read tool in the Ms 365 MCP Server, which means it retrieves data without modifying state.
get-planner-task accepts 6 parameters: expand, select, fetchAllPages, plannerTaskId, includeHeaders, excludeResponse. Required: plannerTaskId. 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-planner-task: 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-planner-task 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-planner-task 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-planner-task. 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-planner-task 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