migration_dry_run
List pending SQLite migrations without applying them.
This record as markdown: /tools/todos/migration-dry-run.md
What migration_dry_run does on Todos
AI agents call migration_dry_run to retrieve information from Todos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why migration_dry_run is rated Low
The tool only lists/reads pending migrations but explicitly does not apply them, making it a pure read operation with no side effects.
From the tool's definition List pending SQLite migrations without applying them
Attacks that exploit this kind of access
The rule that runs migration_dry_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For migration_dry_run, this is the rule to start with:
migration_dry_run is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every migration_dry_run call is checked against it from then on.
Questions about migration_dry_run
List pending SQLite migrations without applying them. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.
Register the Todos MCP server in PolicyLayer and add a rule for migration_dry_run: 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 Todos. Nothing to install.
migration_dry_run 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 migration_dry_run 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 migration_dry_run. 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.
migration_dry_run is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todos, and thousands of servers like it.
This server
Across the catalogue