데이터베이스 스키마를 Mermaid ERD 다이어그램으로 생성합니다.
AI agents use generate_schema_mermaid to create or update resources in MCP Database Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Database Server environment.
An AI agent can call generate_schema_mermaid faster than any human can review — one bad instruction and it creates or modifies resources in MCP Database Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
데이터베이스 스키마를 Mermaid ERD 다이어그램으로 생성합니다. It is categorised as a Write tool in the MCP Database Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Database Server MCP server in PolicyLayer and add a rule for generate_schema_mermaid: 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 MCP Database Server. Nothing to install.
generate_schema_mermaid 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 generate_schema_mermaid 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 generate_schema_mermaid. 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.
generate_schema_mermaid is provided by the MCP Database Server MCP server (zerogon1203/db-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.