The prisma migrate status command looks up the migrations in ./prisma/migrations/* folder and the entries in the _prisma_migrations table and compiles information about the state of the migrations in your database. Example output: Status 3 migrations found in prisma/migrations Your local migratio...
AI agents call migrate-status to retrieve information from Prisma MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
migrate-status only reads and reports on migration state by comparing local files against the database table. It does not modify, execute, or delete anything. Low severity because misuse only reveals schema migration metadata.
From the tool's definition 'looks up the migrations' and 'compiles information about the state of the migrations' — purely informational query with no side effects
Documented attack patterns abuse exactly the kind of access migrate-status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prisma MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for migrate-status:
{
"version": "1",
"default": "deny",
"tools": {
"migrate-status": {}
}
}migrate-status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
The prisma migrate status command looks up the migrations in ./prisma/migrations/* folder and the entries in the _prisma_migrations table and compiles information about the state of the migrations in your database. Example output: Status 3 migrations found in prisma/migrations Your local migration history and the migrations table from your database are different: The last common migration is: 20201127134938_new_migration The migration have not yet been applied: 20201208100950_test_migration The migrations from the database are not found locally in prisma/migrations: 20201208100950_new_migration. It is categorised as a Read tool in the Prisma MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prisma MCP Server MCP server in PolicyLayer and add a rule for migrate-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 Prisma MCP Server. Nothing to install.
migrate-status 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 migrate-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.
Set action: deny in the PolicyLayer policy for migrate-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.
migrate-status is provided by the Prisma MCP Server MCP server (prisma/prisma). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Prisma MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Prisma MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.