phone_project_import · Yaver MCP: Risk & Policy

WHAT IT DOES

What phone_project_import does on Yaver

AI agents use phone_project_import 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	—	Optional slug override on import
`skip_seed`	boolean	—	Restore schema/auth but skip seed/live data application
`on_conflict`	string	—	reject \| rename \| overwrite
`tarball_b64`	string	Yes	Base64-encoded .tgz produced by phone_project_export

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why phone_project_import needs a policy

An AI agent can call phone_project_import 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_import Rate-limited

phone_project_import 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_import": {
      "limits": [
        {
          "counter": "phone_project_import_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_import

What does the phone_project_import tool do? +

Import a previously exported phone project tgz (base64-encoded). This restores a local SQLite-backed phone sandbox on this agent without promoting it anywhere else. 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_import accept? +

phone_project_import accepts 4 parameters: slug, skip_seed, on_conflict, tarball_b64. Required: tarball_b64. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on phone_project_import? +

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

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

Can I rate-limit phone_project_import? +

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

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

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