AI agents use create-task 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 new tasks, which is a reversible write operation. It modifies state by adding records but does not delete, destroy, or execute arbitrary code. The blast radius is medium because task creation could spam a plan or clutter task lists, but the impact is easily reversible through the sibling 'delete-task' tool. No financial or destructive capability is present.
From the tool's definition Tool name is 'create-task' and description states 'Create a new task in a Planner plan'. This is a create operation that adds new data to Microsoft Planner.
Documented attack patterns abuse exactly the kind of access create-task 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 create-task:
{
"version": "1",
"default": "deny",
"tools": {
"create-task": {
"limits": [
{
"counter": "create-task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-task 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.
Create a new task in a Planner plan. 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 create-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 Microsoft Planner MCP. Nothing to install.
create-task 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 create-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 create-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.
create-task 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.