Get size information for the database and its tables
AI agents call get_database_size to retrieve information from PostgreSQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches informational metrics (database and table sizes) which is a read-only operation. It has no side effects, cannot modify data, execute commands, or cause destructive changes. The blast radius of misuse is minimal—an AI agent could only retrieve storage statistics, which poses no security risk beyond potential information disclosure of database structure scale.
From the tool's definition Tool name 'get_database_size' and description 'Get size information for the database and its tables' indicate a query operation that retrieves metadata without modifying, executing arbitrary code, or destructively altering data.
Attacks that exploit this kind of access
Get size information for the database and its tables. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for get_database_size: 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 MCP Server. Nothing to install.
get_database_size 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_size 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_size. 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_size is provided by the PostgreSQL MCP Server MCP server (reckersai/mcpg). 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 →