pocketbase-update-record · PocketBase MCP Server MCP

WHAT IT DOES

What pocketbase-update-record does on PocketBase MCP Server

AI agents use pocketbase-update-record 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-update-record needs a policy

This tool modifies existing data reversibly by updating records in a database collection. It is a classic Write operation—creating or modifying data without permanent deletion. Severity is medium because unauthorized updates could corrupt data or expose sensitive information, but changes remain reversible through additional updates or rollbacks.

From the tool's definition Tool name 'pocketbase-update-record' and description 'Met à jour un record existant dans une collection PocketBase' (Updates an existing record in a PocketBase collection) indicate modification of data in a database collection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pocketbase-update-record Rate-limited

pocketbase-update-record 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-update-record": {
      "limits": [
        {
          "counter": "pocketbase-update-record_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-update-record

What does the pocketbase-update-record tool do? +

Met à jour un record existant dans une collection PocketBase. 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-update-record? +

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

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

Can I rate-limit pocketbase-update-record? +

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

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

pocketbase-update-record 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.