Upload un fichier vers une collection PocketBase
AI agents use pocketbase-upload-file 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.
File upload is a reversible write operation that modifies collection state by adding a new file record. It does not execute arbitrary code, delete data, or move money. While files could potentially be overwritten, the core operation is creating/adding data rather than destructively replacing it.
From the tool's definition Tool name 'pocketbase-upload-file' and description 'Upload un fichier vers une collection PocketBase' (Upload a file to a PocketBase collection) indicates the tool creates/adds file data to a collection.
Attacks that exploit this kind of access
Upload un fichier vers 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.
Register the PocketBase MCP Server MCP server in PolicyLayer and add a rule for pocketbase-upload-file: 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-upload-file 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 pocketbase-upload-file 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-upload-file. 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-upload-file 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 →