migrations_status

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

SERVERAppaloft SOURCE@appaloft/mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What migrations_status does on Appaloft

AI agents call migrations_status to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`plan`	object	Yes
`receipts`	array	Yes

Parameters from the server's own tool schema.

RISK

Why migrations_status is rated Low

Even though migrations_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts freeform code/query input (plan.blockers[].code) · Accepts file system path (plan.blockers[].path) · High parameter count (26 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs migrations_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For migrations_status, this is the rule to start with:

migrations_status Allowed

migrations_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "migrations_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every migrations_status call is checked against it from then on.

FAQ

Questions about migrations_status

What does the migrations_status tool do? +

Read migrations.status through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.

What parameters does migrations_status accept? +

migrations_status accepts 2 parameters: plan, receipts. Required: plan, receipts. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on migrations_status? +

Register the Appaloft MCP server in PolicyLayer and add a rule for migrations_status: 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_status? +

migrations_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit migrations_status? +

Yes. Add a rate_limit block to the migrations_status 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_status completely? +

Set action: deny in the PolicyLayer policy for migrations_status. 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_status? +

migrations_status 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.

KEEP EXPLORING

More on Appaloft, and thousands of servers like it.

This server

All 428 Appaloft tools →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →