Open Prisma Studio to view data in your database in a pleasing visual ui. Provide the current working directory of the users project. This should be the top level directory of the project.
AI agents call Prisma-Studio to retrieve information from Prisma MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Prisma Studio is a GUI viewer for examining database records. While it requires the project directory path as input, its stated function is purely observational—viewing existing data. No mutation, deletion, or code execution capabilities are described.
From the tool's definition Tool description states 'view data in your database' and 'visual ui' with no mention of creating, modifying, or deleting data. Prisma Studio is a read-only browser interface for inspecting database contents.
Documented attack patterns abuse exactly the kind of access Prisma-Studio gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prisma MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for Prisma-Studio:
{
"version": "1",
"default": "deny",
"tools": {
"Prisma-Studio": {}
}
}Prisma-Studio is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open Prisma Studio to view data in your database in a pleasing visual ui. Provide the current working directory of the users project. This should be the top level directory of the project. It is categorised as a Read tool in the Prisma MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prisma MCP Server MCP server in PolicyLayer and add a rule for Prisma-Studio: 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 Prisma MCP Server. Nothing to install.
Prisma-Studio 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-Studio 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-Studio. 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-Studio is provided by the Prisma MCP Server MCP server (prisma/prisma). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Prisma MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Prisma MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.