mcp_get_connection_details
Get detailed MongoDB connection information.
This record as markdown: /tools/441126098-mongo-mcp/mcp-get-connection-details.md
What mcp_get_connection_details does on Mongo-MCP
AI agents call mcp_get_connection_details to retrieve information from Mongo-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mcp_get_connection_details is rated Low
This tool retrieves connection details (host, port, credentials, authentication settings, etc.) without creating, modifying, or deleting data. It is a read operation. Severity is high because exposed connection details could enable an attacker to directly access the MongoDB instance if credentials are included in the returned information, even though the tool itself performs no destructive action.
From the tool's definition Tool name 'mcp_get_connection_details' and description 'Get detailed MongoDB connection information' indicate retrieval of connection metadata without modification.
Attacks that exploit this kind of access
The rule that runs mcp_get_connection_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mongo-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_get_connection_details, this is the rule to start with:
mcp_get_connection_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mongo-MCP, apply this rule, and every mcp_get_connection_details call is checked against it from then on.
Questions about mcp_get_connection_details
Get detailed MongoDB connection information. It is categorised as a Read tool in the Mongo-MCP MCP Server, which means it retrieves data without modifying state.
Register the Mongo MCP server in PolicyLayer and add a rule for mcp_get_connection_details: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mongo-MCP. Nothing to install.
mcp_get_connection_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mcp_get_connection_details rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for mcp_get_connection_details. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
mcp_get_connection_details is provided by the Mongo MCP server (441126098/mongo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mongo, and thousands of servers like it.
This server
Across the catalogue