This record as markdown: /tools/io-github-kivanccakmak-yaver/backend-collection-create.md
What backend_collection_create does on Yaver
AI agents use backend_collection_create to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
type | string | — | Collection type: base, auth, view (default: base) |
schema | array | — | Array of field definitions |
Parameters from the server's own tool schema.
Why backend_collection_create is rated Medium
Creating a PocketBase collection is a Write operation: it modifies backend state by adding a new data structure, but the action is reversible (collections can be deleted). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool name 'backend_collection_create' and description 'Create a PocketBase collection' indicate creation of a new database collection, which is a reversible data structure modification.
Attacks that exploit this kind of access
The rule that runs backend_collection_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For backend_collection_create, this is the rule to start with:
backend_collection_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every backend_collection_create call is checked against it from then on.
Questions about backend_collection_create
Create a PocketBase collection. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
backend_collection_create accepts 3 parameters: name, type, schema. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for backend_collection_create: 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 Yaver. Nothing to install.
backend_collection_create 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 backend_collection_create 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 backend_collection_create. 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.
backend_collection_create is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue