Docs
MCP security best practices
MCP gives AI operational power, so RedMate separates account credentials, network exposure, and write side effects.
Security boundaries
- Local access
- The MCP server binds to 127.0.0.1 by default and only accepts localhost, 127.0.0.1, or ::1 Host values. External networks cannot connect directly.
- Credentials
- Tool responses never return cookies, tokens, or QR login payloads. Account sessions remain inside RedMate's local isolated browser.
- Write tools
- Deleting, publishing, cancelling tasks, and updating drafts are marked destructive so clients can require confirmation before calling them.
- Idempotency
- Publishing and scheduling tools support idempotency_key so agent retries do not duplicate publishing actions.