AI agents call get_database_version to retrieve information from PostgreSQL SSH MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves version information from the PostgreSQL server—a read-only operation with no side effects. It does not execute arbitrary queries, modify data, or trigger external operations. The blast radius of misuse is minimal; an attacker could only learn the PostgreSQL version, which is already often publicly discoverable. It poses no integrity, availability, or financial risk.
From the tool's definition Tool name 'get_database_version' and description 'Get PostgreSQL server version' indicate a query operation that retrieves metadata without modifying or executing arbitrary code.
Documented attack patterns abuse exactly the kind of access get_database_version gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PostgreSQL SSH MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_database_version:
{
"version": "1",
"default": "deny",
"tools": {
"get_database_version": {}
}
}get_database_version is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get PostgreSQL server version. It is categorised as a Read tool in the PostgreSQL SSH MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL SSH MCP Server MCP server in PolicyLayer and add a rule for get_database_version: 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 PostgreSQL SSH MCP Server. Nothing to install.
get_database_version 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_database_version 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_database_version. 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_database_version is provided by the PostgreSQL SSH MCP Server MCP server (zlash65/postgresql-ssh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PostgreSQL SSH MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 PostgreSQL SSH MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.