AI agents call get_schema_names to retrieve information from Pgsql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves schema metadata without side effects, modification, or execution. It poses minimal risk as it only exposes structural information about the database. Severity is low because schema names are typically non-sensitive metadata and the operation cannot cause damage or unintended state changes.
From the tool's definition Tool name 'get_schema_names' and description 'Get all schema names' indicate a retrieval operation with no modification or execution of arbitrary code.
Documented attack patterns abuse exactly the kind of access get_schema_names gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pgsql, and nothing reaches the server without passing your rules. This is the rule we recommend for get_schema_names:
{
"version": "1",
"default": "deny",
"tools": {
"get_schema_names": {}
}
} get_schema_names 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 all schema names. It is categorised as a Read tool in the Pgsql MCP Server, which means it retrieves data without modifying state.
Register the Pgsql MCP server in PolicyLayer and add a rule for get_schema_names: 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 Pgsql. Nothing to install.
get_schema_names 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_schema_names 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_schema_names. 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_schema_names is provided by the Pgsql MCP server (twn39/pgsql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pgsql, 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.
9 Pgsql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.