Génère une migration pour ajouter, modifier ou supprimer des champs d\
AI agents call pocketbase-update-collection-fields to permanently remove resources in PocketBase MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool spans Write and Destructive categories because it can add/modify fields (reversible) but also delete fields (irreversible, potentially causing data loss). Per the rules, Destructive is the most severe applicable category. Deleting schema fields in a database can permanently destroy data stored in those columns, making this high severity.
From the tool's definition 'supprimer des champs' (delete fields) — the tool generates migrations that can add, modify, or delete collection fields, including irreversible deletion of schema fields
Attacks that exploit this kind of access
Génère une migration pour ajouter, modifier ou supprimer des champs d\. It is categorised as a Destructive tool in the PocketBase MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PocketBase MCP Server MCP server in PolicyLayer and add a rule for pocketbase-update-collection-fields: 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.
pocketbase-update-collection-fields is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pocketbase-update-collection-fields 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 pocketbase-update-collection-fields. 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.
pocketbase-update-collection-fields 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →