100+ MCP tools. Security built into each one.
Connect Claude Code, Codex, Claude Desktop, or any MCP-compatible client and work through 100+ tools with Tadpole's permission model, masking, and audit built in. The AI touches your databases only through these tools — no extra security setup.
MCP tools with policy built in
100+ MCP tools with Tadpole DB Hub's permission model, DLP filters, and audit logging applied. The AI reaches your databases only through them, and every call passes RBAC, masking, approval, and audit — no exceptions.
From queries to ops and security — 100+ tools
Every tool passes Tadpole's RBAC, masking, approval, and audit the moment it's called. The AI works your databases only through these tools — no extra security setup.
Explore & Query
Browse schemas, tables, and data in plain English.
Ops & Diagnostics
Inspect slow queries, locks, and sessions; diagnose performance.
Security & Governance
Masking, permissions, and policy enforced at the tool-call layer.
Approval Workflow
High-risk actions run only after an approver settles them.
Audit & Reporting
Every call logged with user and intent, exported as reports.
Change & Admin
Schema changes, migrations, and user/DB management.
All of these — 100+ tools in total — run under the same security policy.
Your role
shapes the toolset.
Even on the same MCP server, the tools exposed depend on the connected user's role. USER gets query and approval tools, DBA adds ops and policy, SYSTEM_ADMIN adds user and security management — tools outside your role never even appear in the list.
Tools outside your role are dropped from the tools/list response.
Every tool
passes policy.
Whichever tool the AI calls, it passes the same RBAC, masking, and approval workflows as humans. High-risk SQL never runs without an approval.
⏺ Let me first fetch the approver candidates. Called tadpole-mcp (ctrl+o to expand)⏺ Found 2 approver candidates. Pick one to send the request to. user_seqnamemaster 18Min-Ji KimNO 1Seo-Jun ParkYES (master)⎿ User: Seo-Jun Park (seq=1, master) Called tadpole-mcp (ctrl+o to expand)⏺ Settle request created. seq56 (group_seq=3000915) targetSELECT * FROM sample_db.customer LIMIT 10 approverSeo-Jun Park (seq=1, master) modeONE_TIME Once Seo-Jun approves, run /settle execute 56 to execute.※ recap: Querying 10 sample rows from sample_db.customer in TadpoleDBHub. SELECT needs approval, so settle request seq=56 was sent to Seo-Jun Park (master). Next: run /settle execute 56 once approved. (disable recaps in /config)✻ Cooked for 23s · Claude Opus 4.7Works for your entire team
Ship with AI, govern like always
Your AI tools query databases through the same permission model your team already uses.
Full visibility into AI activity
Every AI query is attributed to a user, logged with intent, and searchable alongside manual queries.
Masking and approvals always on
Sensitive data masking and high-risk approval workflows apply to AI queries automatically.
AI meets your security model.
Join teams using TadpoleHub to let AI access databases without sacrificing control.