This record as markdown: /tools/io-github-kivanccakmak-yaver/db-seed.md
What db_seed does on Yaver
AI agents invoke db_seed to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why db_seed is rated High
This tool executes a database seed file, which performs database operations (typically INSERT, CREATE, or UPDATE statements). While seeds are often used for legitimate development setup, this is an Execute risk because: (1) it runs code whose effects depend on the seed file's contents, (2) it modifies database state irreversibly in many cases, (3) a compromised or malicious seed file could corrupt or exfiltrate data.
From the tool's definition Tool name 'db_seed' and description 'Run database seed file' indicate execution of a database seed script, which runs code with side effects.
Attacks that exploit this kind of access
The rule that runs db_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 db_seed, this is the rule to start with:
db_seed stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 db_seed call is checked against it from then on.
Questions about db_seed
Run database seed file. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Yaver MCP server in PolicyLayer and add a rule for db_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.
db_seed is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the db_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 db_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.
db_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.
Across the catalogue