pocketbase-execute-migration · PocketBase MCP Server MCP

WHAT IT DOES

What pocketbase-execute-migration does on PocketBase MCP Server

AI agents invoke pocketbase-execute-migration to trigger actions in PocketBase MCP Server. 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 IT NEEDS A POLICY

Why pocketbase-execute-migration needs a policy

This tool executes arbitrary database migrations, which can modify or delete schema structures. While destructive operations are possible (collections can be deleted), the tool itself is an execution mechanism whose effects depend on the migration argument provided. It triggers external database operations that modify state irreversibly.

From the tool's definition Tool name 'pocketbase-execute-migration' and description indicating it applies/executes a migration. The French phrase 'Applique une migration via l' translates to 'Applies a migration via...', confirming execution of database schema changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pocketbase-execute-migration Rate-limited

pocketbase-execute-migration 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pocketbase-execute-migration": {
      "limits": [
        {
          "counter": "pocketbase-execute-migration_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PocketBase MCP Server, so you can run agents against it safely.

FAQ

Questions about pocketbase-execute-migration

What does the pocketbase-execute-migration tool do? +

Applique une migration via l\. It is categorised as a Execute tool in the PocketBase MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pocketbase-execute-migration? +

Register the PocketBase MCP Server MCP server in PolicyLayer and add a rule for pocketbase-execute-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.

What risk level is pocketbase-execute-migration? +

pocketbase-execute-migration is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pocketbase-execute-migration? +

Yes. Add a rate_limit block to the pocketbase-execute-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.

How do I block pocketbase-execute-migration completely? +

Set action: deny in the PolicyLayer policy for pocketbase-execute-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.

What MCP server provides pocketbase-execute-migration? +

pocketbase-execute-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.