Génère une migration pour revenir en arrière sur une migration précédente
AI agents call pocketbase-revert-migration to permanently remove resources in PocketBase MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Reverting a database migration typically involves dropping collections, fields, or data that were created by the original migration. Such operations are generally irreversible, placing this in the Destructive category. The blast radius is high because it can affect schema structure and existing data across an entire collection.
From the tool's definition 'revenir en arrière sur une migration précédente' (revert a previous migration) — reverting a migration can drop fields, tables, or data irreversibly
Attacks that exploit this kind of access
Génère une migration pour revenir en arrière sur une migration précédente. It is categorised as a Destructive tool in the PocketBase MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PocketBase MCP Server MCP server in PolicyLayer and add a rule for pocketbase-revert-migration: 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 PocketBase MCP Server. Nothing to install.
pocketbase-revert-migration is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pocketbase-revert-migration 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 pocketbase-revert-migration. 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.
pocketbase-revert-migration is provided by the PocketBase MCP Server MCP server (step-by-step-technology/pocketbase-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 →