The server authenticates to another system with a key, token or connection string. Its reach is whatever that credential reaches, inherited by every agent allowed to call it. Published by MCP reference example.
Taken from the official documentation linked at the bottom.
| Field | Value |
|---|---|
| Publisher | MCP reference example |
| Authentication | A database connection string, for example postgresql://localhost/mydb. |
| What it holds | A database identity. The connection string carries the credential. |
| What that reaches | Everything the database role in that connection string is allowed to do. A role used for convenience during development frequently has more than read access. |
| Risk class | Holds a credential The server authenticates to another system with a key, token or connection string. Its reach is whatever that credential reaches, inherited by every agent allowed to call it. |
A connection string is a credential that looks like configuration, which is why it ends up in files and environment variables that are treated as settings rather than secrets.
Not whether the server is trustworthy. What it holds, and what that reaches.
Which role the string authenticates as, whether it can write, and whether the same string appears in more than one place.
The same questions apply to any server in this database, which is why the MCP server security page is the general version of this page.
Holds a credential
Every field above is taken from the official documentation. Where it does not say, this page does not either.
The two questions this record answers.
A database identity. The connection string carries the credential.
Everything the database role in that connection string is allowed to do. A role used for convenience during development frequently has more than read access.
Book a demo and we walk through the access paths in an environment like yours.