Learning level
94/100
Privacy & Data Minimization
VauPrime MCP · 91–100 · Privacy, Security & HelpGuide type
Security
Audience
Users & builders
Sections
4
Privacy & Data Minimization
MCP guideUnderstand the privacy controls used by VauPrime MCP to keep AI-agent responses purpose-limited and avoid unnecessary personal, internal and diagnostic data exposure.
What this guide covers
Purpose-limited responses
Examples of excluded data
Generic user-facing errors
Privacy policy
Quick facts
ProductVauPrime MCP
ProtocolModel Context Protocol
TransportStreamable HTTP
AccessRead-only tools
Purpose-limited access: VauPrime MCP is designed for authorized, read-only accounting context and minimized structured responses.
01
Purpose-limited responses
VauPrime MCP does not intentionally return raw database or RPC payloads. Each tool defines an output schema for the accounting task it performs.
02
Examples of excluded data
Current minimized outputs remove data that is not required for the tool purpose.
OAuth/access tokens and authentication secrets.
Internal FVS identifiers and internal customer/account database ids.
Unnecessary branch/location metadata.
Customer phone, email, postal address and GSTIN/tax identifiers from current MCP customer reads.
Backend/PostgREST/RPC response bodies, stack traces and fuzzy-match scores.
Raw transaction/manufacturing ids, free-form stock notes and debug-only timestamps/filter echoes.
03
Generic user-facing errors
Tool failures are normalized so backend response bodies, SQL/PostgREST/RPC details, tokens and stack traces are not intentionally exposed to connected clients.
04
Privacy policy
The public VauPrime Privacy Policy describes the broader categories of data processed by VauPrime and connected AI/MCP services: https://www.vauprime.com/privacypolicy
Production endpoint
https://mcp.vauprime.com/mcp