New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

migrations_plan

Read migrations.plan through the Appaloft application operation catalog. Shared with CLI and HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp
Medium RISK CLASS
Category Write
Parameters 11 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/appaloft-mcp/migrations-plan.md

What migrations_plan does on Appaloft

AI agents use migrations_plan to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.

ParameterTypeRequiredDescription
bundle object Yes

Parameters from the server's own tool schema.

Why migrations_plan is rated Medium

An AI agent can call migrations_plan faster than any human can review: one bad instruction and it creates or modifies resources in Appaloft by the hundred, each call as confident as the last.

Risk signalsAccepts freeform code/query input (bundle.spec.sourceBlockers[].code) · Accepts file system path (bundle.spec.sourceBlockers[].path) · Accepts URL/endpoint input (bundle.spec.domains[].hostname) · High parameter count (81 properties)

Questions about migrations_plan

What does the migrations_plan tool do? +

Read migrations.plan through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does migrations_plan accept? +

migrations_plan accepts 1 parameter: bundle. Required: bundle. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on migrations_plan? +

Register the Appaloft MCP server in PolicyLayer and add a rule for migrations_plan: 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 Appaloft. Nothing to install.

What risk level is migrations_plan? +

migrations_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit migrations_plan? +

Yes. Add a rate_limit block to the migrations_plan 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.

How do I block migrations_plan completely? +

Set action: deny in the PolicyLayer policy for migrations_plan. 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.

What MCP server provides migrations_plan? +

migrations_plan is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Appaloft, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Appaloft's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.