AI agents call migrate-status to retrieve information from MCP Atlas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only reads and reports the current migration status of a database. It does not apply, modify, or delete anything. This is a pure read/query operation analogous to checking which migrations have been applied.
From the tool's definition 'Report current migration status of a database' — purely reporting/querying status with no side effects
Attacks that exploit this kind of access
Report current migration status of a database. It is categorised as a Read tool in the MCP Atlas MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlas 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 MCP Atlas. 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 MCP Atlas MCP server (mpreziuso/mcp-atlas). 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 →