Get extended task details including description and checklist
AI agents call get-task-details to retrieve information from Microsoft Planner MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval operation with no side effects. It queries existing task metadata without creating, modifying, deleting, or executing external operations. The blast radius of misuse is minimal—an agent retrieving unauthorized task details could pose a confidentiality risk, but this is a standard Read operation.
From the tool's definition Tool name 'get-task-details' and description 'Get extended task details' indicate retrieval of existing task information. No modifications, deletions, or external actions are performed. Returns data only (description and checklist).
Documented attack patterns abuse exactly the kind of access get-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 get-task-details:
{
"version": "1",
"default": "deny",
"tools": {
"get-task-details": {}
}
}get-task-details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get extended task details including description and checklist. It is categorised as a Read tool in the Microsoft Planner MCP MCP Server, which means it retrieves data without modifying state.
Register the Microsoft Planner MCP server in PolicyLayer and add a rule for get-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.
get-task-details 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-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 get-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.
get-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.