phone_project_export · Yaver MCP: Risk & Policy

WHAT IT DOES

What phone_project_export does on Yaver

AI agents use phone_project_export 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.

PARAMETERS

Parameter	Type	Required	Description
`slug`	string	Yes
`containerize`	boolean	—	Include Dockerfile/docker-compose/.env scaffold for own-cloud or Yaver Cloud deploy paths
`include_data`	boolean	—	Include local.db so runtime rows survive import/push

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why phone_project_export needs a policy

An AI agent can call phone_project_export faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

phone_project_export Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "phone_project_export": {
      "limits": [
        {
          "counter": "phone_project_export_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about phone_project_export

What does the phone_project_export tool do? +

Return a tgz of the project's portable manifest (schema + auth + seed + config + generated DDL). Base64-encoded so it round-trips through JSON. Supports include_data and containerize so MCP clients can export the exact same local-first backend bundle the mobile app and CLI use. 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.

What parameters does phone_project_export accept? +

phone_project_export accepts 3 parameters: slug, containerize, include_data. Required: slug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on phone_project_export? +

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

phone_project_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit phone_project_export? +

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

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

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