This record as markdown: /tools/io-github-kivanccakmak-yaver/prisma-status.md
What prisma_status does on Yaver
AI agents call prisma_status 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why prisma_status is rated Low
This tool retrieves and displays the current status of Prisma migrations. It is a read-only operation with no side effects—it does not create, modify, delete, or execute migrations, only reports on their state. The low severity reflects that misuse cannot cause damage; at worst, an agent could repeatedly query the status.
From the tool's definition Tool name 'prisma_status' and description 'Show Prisma migration status' indicate a query operation that displays information about database migrations without modifying state.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs prisma_status 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 prisma_status, this is the rule to start with:
prisma_status is read-only, so it stays allowed. 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 prisma_status call is checked against it from then on.
Questions about prisma_status
Show Prisma migration status. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
prisma_status accepts 1 parameter: directory. 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 prisma_status: 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.
prisma_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the prisma_status 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 prisma_status. 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.
prisma_status 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