PostgreSQL_get_materialized_views
List all materialized views in a schema.
This record as markdown: /tools/mukul975-postgres-mcp-server/postgresql-get-materialized-views.md
What PostgreSQL_get_materialized_views does on Postgres
AI agents call PostgreSQL_get_materialized_views 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.
Why PostgreSQL_get_materialized_views is rated Low
The tool performs a simple enumeration/list operation on materialized views, which is a non-destructive read of database metadata. It has no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—exposing materialized view names poses no financial, operational, or security risk to the database itself.
From the tool's definition Tool description: 'List all materialized views in a schema.' This is a read-only query operation that retrieves schema metadata without modifying any data.
Attacks that exploit this kind of access
The rule that runs PostgreSQL_get_materialized_views 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_materialized_views, this is the rule to start with:
PostgreSQL_get_materialized_views is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Postgres, apply this rule, and every PostgreSQL_get_materialized_views call is checked against it from then on.
Questions about PostgreSQL_get_materialized_views
List all materialized views in a schema. It is categorised as a Read tool in the Postgres MCP Server, which means it retrieves data without modifying state.
Register the Postgres MCP server in PolicyLayer and add a rule for PostgreSQL_get_materialized_views: 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.
PostgreSQL_get_materialized_views 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 PostgreSQL_get_materialized_views 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 PostgreSQL_get_materialized_views. 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.
PostgreSQL_get_materialized_views 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.
More on Postgres, and thousands of servers like it.
This server
Across the catalogue