List migrations: applied (in DB) and pending (files not yet applied). Use to sync database.
AI agents call db_list_migrations to retrieve information from Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool lists existing migrations for informational purposes only—it retrieves the state of applied and pending migrations without creating, modifying, deleting, or executing any database operations. This is a read-only query with no side effects, fitting the 'Read' category. Severity is low because listing migrations poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'db_list_migrations' and description 'List migrations: applied (in DB) and pending (files not yet applied).
Attacks that exploit this kind of access
List migrations: applied (in DB) and pending (files not yet applied). Use to sync database. It is categorised as a Read tool in the Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Database MCP Server MCP server in PolicyLayer and add a rule for db_list_migrations: 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 Database MCP Server. Nothing to install.
db_list_migrations 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 db_list_migrations 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 db_list_migrations. 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.
db_list_migrations is provided by the Database MCP Server MCP server (roilanrodriguez55/database-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →