pocketbase-add-field-migration · PocketBase MCP Server MCP

WHAT IT DOES

What pocketbase-add-field-migration does on PocketBase MCP Server

AI agents use pocketbase-add-field-migration to create or update resources in PocketBase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PocketBase MCP Server environment.

WHY IT NEEDS A POLICY

Why pocketbase-add-field-migration needs a policy

Adding a field to a collection is a Write operation—it creates a new schema element and modifies the database structure, but the change is reversible (the field can be removed or the migration rolled back). Severity is medium because schema modifications can affect application behavior and data integrity, but the operation itself is not destructive or irreversible.

From the tool's definition Tool description states 'Génère une migration pour ajouter un seul champ à une collection existante' — it generates a migration to add a field, which modifies database schema.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pocketbase-add-field-migration Rate-limited

pocketbase-add-field-migration stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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-add-field-migration": {
      "limits": [
        {
          "counter": "pocketbase-add-field-migration_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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-add-field-migration

What does the pocketbase-add-field-migration tool do? +

Génère une migration pour ajouter un seul champ à une collection existante. It is categorised as a Write tool in the PocketBase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

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

Register the PocketBase MCP Server MCP server in PolicyLayer and add a rule for pocketbase-add-field-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-add-field-migration? +

pocketbase-add-field-migration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pocketbase-add-field-migration? +

Yes. Add a rate_limit block to the pocketbase-add-field-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-add-field-migration completely? +

Set action: deny in the PolicyLayer policy for pocketbase-add-field-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-add-field-migration? +

pocketbase-add-field-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.