Export all visible Microsoft To Do lists, tasks, and checklist items to a local JSON backup file.
AI agents call export_backup to retrieve information from Microsoft Todo Safe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads/retrieves data from Microsoft To Do and writes it to a local backup file. While it writes a file locally, its primary action is reading/exporting existing data with no modification to the source data. The local file write is a side effect of the export operation, and since it only captures existing data without modifying the To Do system, Read is the most appropriate category.
From the tool's definition Export all visible Microsoft To Do lists, tasks, and checklist items to a local JSON backup file
Attacks that exploit this kind of access
Export all visible Microsoft To Do lists, tasks, and checklist items to a local JSON backup file. It is categorised as a Read tool in the Microsoft Todo Safe MCP Server, which means it retrieves data without modifying state.
Register the Microsoft Todo Safe MCP server in PolicyLayer and add a rule for export_backup: 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 Safe. Nothing to install.
export_backup 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 export_backup 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 export_backup. 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.
export_backup is provided by the Microsoft Todo Safe MCP server (saenai/microsoft-todo-safe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →