system_db_migrate
Run system.db-migrate through the Appaloft application operation catalog. Shared with CLI.
This record as markdown: /tools/appaloft-mcp/system-db-migrate.md
What system_db_migrate does on Appaloft
AI agents invoke system_db_migrate to trigger actions in Appaloft. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why system_db_migrate is rated High
This tool runs a database migration operation, which executes schema changes against a database. Database migrations can create, alter, or drop tables/columns and are often irreversible. The 'run' verb and 'db-migrate' name indicate execution of an operation with potentially destructive side effects.
From the tool's definition "Run system.db-migrate through the Appaloft application operation catalog"
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_db_migrate 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 system_db_migrate, this is the rule to start with:
system_db_migrate stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every system_db_migrate call is checked against it from then on.
Questions about system_db_migrate
Run system.db-migrate through the Appaloft application operation catalog. Shared with CLI. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Appaloft MCP server in PolicyLayer and add a rule for system_db_migrate: 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.
system_db_migrate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the system_db_migrate 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 system_db_migrate. 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.
system_db_migrate 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.
Across the catalogue