backend_setup

Get PocketBase SDK integration code for your framework.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/backend-setup.md

WHAT IT DOES

What backend_setup does on Yaver

AI agents call backend_setup to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`framework`	string	—	Framework: javascript, dart, react

Parameters from the server's own tool schema.

RISK

Why backend_setup is rated Low

The tool fetches pre-generated SDK integration code for a given framework. It is a read/query operation that returns information (code templates) without writing to any system, executing code, or causing side effects.

From the tool's definition 'Get PocketBase SDK integration code for your framework' — retrieves/returns code snippets without executing or modifying anything

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs backend_setup 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_setup, this is the rule to start with:

backend_setup Allowed

backend_setup is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "backend_setup": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every backend_setup call is checked against it from then on.

FAQ

Questions about backend_setup

What does the backend_setup tool do? +

Get PocketBase SDK integration code for your framework. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does backend_setup accept? +

backend_setup accepts 1 parameter: framework. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on backend_setup? +

Register the Yaver MCP server in PolicyLayer and add a rule for backend_setup: 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.

What risk level is backend_setup? +

backend_setup is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit backend_setup? +

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

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

backend_setup 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →