Security
RapidMCP holds your team's API keys so your teammates never have to. Here's exactly how they're protected, and how you control who uses them.
Your keys
- Secrets are encrypted at rest with AES-256-GCM, each with its own random IV, using a key held outside the database.
- They're write-only. Once saved, nobody can read a value back: not you, not your teammates, not your agent, not our dashboard.
- Each tool declares the secrets it uses, and only those are given to it while it runs. Other tools never see them.
- Values are redacted from tool results and logs, including common encodings (base64, URL and hex).
- Agents can ask for a secret, but never receive it. The person adds it through a link to RapidMCP, never by pasting it into a chat.
Who can use your MCPs
- Every MCP is protected by OAuth 2.1 with PKCE. Each teammate signs in as themselves; there are no shared API keys or headers to hand around.
- You choose who can use each MCP: your project only, people you approve, or anyone signed in.
- Roles keep building and using apart: owners and editors change tools, everyone else only uses them.
- Revoke a person or disconnect every app from an MCP in one click. Their access stops straight away.
- Access tokens last an hour, and each MCP's tokens only work for that MCP.
Seeing what happened
- Every tool call and every change (who saved what, published, rolled back or added a secret) shows up in the MCP's live activity log.
- Every saved version of every tool is kept, with diffs, and you can roll back for everyone in seconds.
- With drafts on, changes don't reach your team until an owner or editor publishes them.
Where code runs
- Tools run in isolated, short-lived sandboxes that are destroyed after each call. No tool shares a machine or memory with another customer's.
- Tools have a time limit, and only the secrets and settings they declare are passed in.
Reviewing us for your company?
Our trust center has our policies and answers to common security questionnaires. For anything else, or to run RapidMCP on your own infrastructure (self-hosted), email us.