get_server_info

What get_server_info does on Mcpg

AI agents call get_server_info to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_server_info is rated Low

The tool name pattern 'get_' is consistent with retrieval operations that query state without causing side effects. In the context of a PostgreSQL MCP server, retrieving server metadata (version, configuration, status) is a standard read-only operation. No write, execute, destructive, or financial implications are evident from the name alone.

From the tool's definition Tool name 'get_server_info' indicates retrieval of server information without modification. The empty description prevents confirmation of side effects, but the semantic naming strongly suggests a read-only query operation.

The rule that runs get_server_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_server_info, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_server_info": {}
  }
}

Questions about get_server_info