Update an existing record in a PocketBase collection. Only provided fields will be updated.
AI agents use 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.
This tool modifies existing data (update operation) but does not permanently delete or destroy records. The changes are reversible through subsequent updates or restoration mechanisms. It is less severe than Destructive operations (which cannot be undone) but more impactful than Read operations.
From the tool's definition Tool name 'update_record' and description states it 'Update[s] an existing record', which is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access update_record gives an agent:
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_record:
{
"version": "1",
"default": "deny",
"tools": {
"update_record": {
"limits": [
{
"counter": "update_record_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Update an existing record in a PocketBase collection. Only provided fields will be updated. 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.
Register the PocketBase MCP Server MCP server in PolicyLayer and add a rule for 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.
update_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
update_record is provided by the PocketBase MCP Server MCP server (ssakone/pb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 PocketBase MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 PocketBase MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.