PostgreSQL_get_functions

Get all user-defined functions in the database.

SERVERPostgres SOURCEmukul975/postgres-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mukul975-postgres-mcp-server/postgresql-get-functions.md

WHAT IT DOES

What PostgreSQL_get_functions does on Postgres

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

RISK

Why PostgreSQL_get_functions is rated Low

This tool queries metadata about user-defined functions and returns information without creating, modifying, deleting, or executing any functions or data. It is a passive read operation with minimal blast radius if misused by an AI agent, as it only exposes function definitions/metadata that are typically needed for database management and monitoring tasks.

From the tool's definition Tool description states 'Get all user-defined functions in the database' — a retrieval operation with no modification or execution capability.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs PostgreSQL_get_functions safely

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

PostgreSQL_get_functions Allowed

PostgreSQL_get_functions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Postgres, apply this rule, and every PostgreSQL_get_functions call is checked against it from then on.

FAQ

Questions about PostgreSQL_get_functions

What does the PostgreSQL_get_functions tool do? +

Get all user-defined functions in the database. It is categorised as a Read tool in the Postgres MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on PostgreSQL_get_functions? +

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

What risk level is PostgreSQL_get_functions? +

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

Can I rate-limit PostgreSQL_get_functions? +

Yes. Add a rate_limit block to the PostgreSQL_get_functions 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 PostgreSQL_get_functions completely? +

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

PostgreSQL_get_functions is provided by the Postgres MCP server (mukul975/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What PostgreSQL_get_functions does on Postgres

Why PostgreSQL_get_functions is rated Low

The rule that runs PostgreSQL_get_functions safely

Questions about PostgreSQL_get_functions

More on Postgres, and thousands of servers like it.