get_db_info

Get an overview of the connected database: PostgreSQL version, database name, total size on disk, number of tables, and current connection info (user, host, port).

Server Mcp Postgres Query lordbasilaiassistant-sudo/mcp-postgres-query
Category Read
Risk class Low
Parameters 00 required

What get_db_info does on Mcp Postgres Query

AI agents call get_db_info to retrieve information from Mcp Postgres Query without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_db_info needs a policy

This tool performs schema and system introspection only. It returns informational data about the database state without creating, modifying, deleting, or executing arbitrary operations. The blast radius of misuse is minimal — an agent learning database structure does not enable destructive or financial harm in isolation. Classified as Read with low severity.

From the tool's definition Tool retrieves database metadata: 'PostgreSQL version, database name, total size on disk, number of tables, and current connection info' — all read-only queries with no modification capability.

Questions about get_db_info

What does the get_db_info tool do? +

Get an overview of the connected database: PostgreSQL version, database name, total size on disk, number of tables, and current connection info (user, host, port). It is categorised as a Read tool in the Mcp Postgres Query MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_db_info? +

Register the Mcp Postgres Query MCP server in PolicyLayer and add a rule for get_db_info: 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 Mcp Postgres Query. Nothing to install.

What risk level is get_db_info? +

get_db_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_db_info? +

Yes. Add a rate_limit block to the get_db_info 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.

How do I block get_db_info completely? +

Set action: deny in the PolicyLayer policy for get_db_info. 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.

What MCP server provides get_db_info? +

get_db_info is provided by the Mcp Postgres Query MCP server (lordbasilaiassistant-sudo/mcp-postgres-query). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.