Reticle can capture MCP traffic that may include:

• tool inputs/outputs
• user prompts/context (depending on what your client/server sends)
• server stderr (stack traces, debug prints)
• export artifacts (JSON/CSV/HAR)

• Treat recordings and exports as sensitive.
• Avoid capturing secrets in shared environments.
• Use test credentials where possible.
• Store exports as protected artifacts (access-controlled).
• Redact before sharing externally.

Reticle inspects traffic. It does not constrain what MCP servers can do.

If you run untrusted servers, use OS/container sandboxing, user permissions, and network controls.