Update task description (use for GitHub links). Auto-fetches ETag.
AI agents use update-task-details to create or update resources in Microsoft Planner MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Microsoft Planner MCP environment.
This tool creates or modifies data reversibly by updating task descriptions in Microsoft Planner. While the change is persistent, it is not destructive (the original data is not deleted, just modified) and can be undone by further updates.
From the tool's definition Tool performs 'Update task description' operation, modifying existing task data in Microsoft Planner. Description states it updates task information (specifically mentioning GitHub links as a use case), which is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access update-task-details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Microsoft Planner MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for update-task-details:
{
"version": "1",
"default": "deny",
"tools": {
"update-task-details": {
"limits": [
{
"counter": "update-task-details_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-task-details 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.
Update task description (use for GitHub links). Auto-fetches ETag. It is categorised as a Write tool in the Microsoft Planner MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Microsoft Planner MCP server in PolicyLayer and add a rule for update-task-details: 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 Microsoft Planner MCP. Nothing to install.
update-task-details 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 update-task-details 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 update-task-details. 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.
update-task-details is provided by the Microsoft Planner MCP server (vyente-ruffin/microsoft-planner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Microsoft Planner MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Microsoft Planner MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.