phone_project_seed
Write rows to a phone project's SQLite file from a seed map {tableName:[{column:value}]}. Uses INSERT OR REPLACE.
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-seed.md
What phone_project_seed does on Yaver
AI agents use phone_project_seed 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 |
|---|---|---|---|
seed | object | Yes | |
slug | string | Yes |
Parameters from the server's own tool schema.
Why phone_project_seed is rated Medium
This tool creates or modifies data in a SQLite database through INSERT OR REPLACE statements. While it modifies persistent state, INSERT OR REPLACE is reversible (data can be updated or deleted later), distinguishing it from irreversible Destructive operations. The local dev context and use of a seed map for initialization suggests typical development workflow rather than production data manipulation.
From the tool's definition Tool description states "Write rows to a phone project's SQLite file" and uses "INSERT OR REPLACE", which are reversible database modification operations.
Attacks that exploit this kind of access
The rule that runs phone_project_seed 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 phone_project_seed, this is the rule to start with:
phone_project_seed 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 phone_project_seed call is checked against it from then on.
Questions about phone_project_seed
Write rows to a phone project's SQLite file from a seed map {tableName:[{column:value}]}. Uses INSERT OR REPLACE. 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.
phone_project_seed accepts 2 parameters: seed, slug. Required: seed, slug. 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 phone_project_seed: 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.
phone_project_seed 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 phone_project_seed 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 phone_project_seed. 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.
phone_project_seed 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