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 My MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries task data from a Microsoft Todo list without side effects. It is a read-only operation that fetches existing data. The 'Get' prefix and retrieval-focused description confirm it belongs in the Read category with low severity, as misuse would only expose data already owned by the user.
From the tool's definition Tool name 'get-tasks' and description 'Get tasks from a specific Microsoft Todo list' indicate data retrieval with no modification or deletion.
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 My MCP, 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 My MCP MCP Server, which means it retrieves data without modifying state.
Register the My 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 My MCP. 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 My MCP server (jordanburke/microsoft-todo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from My 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.
16 My MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.