Get the current server configuration (with sensitive data redacted).
AI agents call get_server_config to retrieve information from Legacy Mongodb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves server configuration metadata for inspection purposes. It performs no write, execute, or destructive operations. The redaction of sensitive data limits the information exposure. This aligns with the Read category as it simply queries and returns configuration state without modifying anything or triggering external operations.
From the tool's definition Tool name 'get_server_config' and description 'Get the current server configuration (with sensitive data redacted)' indicate a read-only retrieval operation.
Attacks that exploit this kind of access
Get the current server configuration (with sensitive data redacted). It is categorised as a Read tool in the Legacy Mongodb MCP Server, which means it retrieves data without modifying state.
Register the Legacy Mongodb MCP server in PolicyLayer and add a rule for get_server_config: 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 Legacy Mongodb. Nothing to install.
get_server_config 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 get_server_config 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 get_server_config. 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.
get_server_config is provided by the Legacy Mongodb MCP server (webxspark/legacy-mongodb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →