update_collection

THE RISK

Medium Risk

Why update_collection needs a policy

This tool modifies database schema definitions (collections) reversibly. While not destructive (changes can theoretically be undone), it affects the structural foundation of the database and requires admin privileges. The blast radius is significant: schema changes can break dependent applications, alter data validation rules, or interfere with other operations.

From the tool's definition 'Update an existing collection in PocketBase (admin only)' - the verb 'update' indicates modification of existing data structure; 'collection' refers to database schema objects; marked admin-only suggesting elevated privilege requirement

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access update_collection gives an agent:

POLICY

How to control update_collection

PolicyLayer is an MCP gateway — it sits between your AI agents and PocketBase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_collection:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_collection": {
      "limits": [
        {
          "counter": "update_collection_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_collection 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.

Create a free account and register PocketBase MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More PocketBase MCP Server tools

Destructive delete_collection Delete a collection from PocketBase (admin only) Destructive delete_record Delete a record Execute impersonate_user Impersonate another user (admin only) Write confirm_password_reset Confirm password reset with token Write request_password_reset Request password reset Write auth_refresh Refresh authentication token Write authenticate_with_oauth2 Authenticate a user with OAuth2 Write authenticate_with_otp Authenticate a user with one-time password

All 24 PocketBase MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_collection

What does the update_collection tool do? +

Update an existing collection in PocketBase (admin only). 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 update_collection? +

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

update_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_collection? +

Yes. Add a rate_limit block to the update_collection 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 update_collection completely? +

Set action: deny in the PolicyLayer policy for update_collection. 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 update_collection? +

update_collection is provided by the PocketBase MCP Server MCP server (mrwyndham/pocketbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PocketBase MCP Server tool call.

Start from PocketBase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →