Get tasks from a specific Microsoft Todo list. These are the main todo items that can contain checklist items (subtasks).
AI agents call get-tasks to retrieve information from Microsoft Todo MCP Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries existing task data from a Microsoft Todo list without creating, modifying, or deleting any data. It is a read-only operation with minimal blast radius if misused by an AI agent—the worst outcome would be unauthorized viewing of task contents.
From the tool's definition Tool name 'get-tasks' and description 'Get tasks from a specific Microsoft Todo list' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get-tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Microsoft Todo MCP Service, and nothing reaches the server without passing your rules. This is the rule we recommend for get-tasks:
{
"version": "1",
"default": "deny",
"tools": {
"get-tasks": {}
}
} get-tasks 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 tasks from a specific Microsoft Todo list. These are the main todo items that can contain checklist items (subtasks). It is categorised as a Read tool in the Microsoft Todo MCP Service MCP Server, which means it retrieves data without modifying state.
Register the Microsoft Todo MCP Service MCP server in PolicyLayer and add a rule for get-tasks: 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 Todo MCP Service. Nothing to install.
get-tasks 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-tasks 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-tasks. 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-tasks is provided by the Microsoft Todo MCP Service MCP server (jhirono/todomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Microsoft Todo MCP Service, 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.
13 Microsoft Todo MCP Service tools catalogued and risk-classified — across an index of 43,000+ MCP servers.