Monitor materialized views status and freshness.
AI agents call monitor_materialized_views to retrieve information from Postgres without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about materialized view states and data freshness but does not create, modify, delete, or execute operations. Monitoring is a read operation with no side effects. Severity is low because misuse would only expose database metadata, not cause operational impact.
From the tool's definition Tool name 'monitor_materialized_views' and description 'Monitor materialized views status and freshness' indicate querying/checking status without modification. Keywords 'monitor' and 'status' are observational, not actionable modifications.
Documented attack patterns abuse exactly the kind of access monitor_materialized_views gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres, and nothing reaches the server without passing your rules. This is the rule we recommend for monitor_materialized_views:
{
"version": "1",
"default": "deny",
"tools": {
"monitor_materialized_views": {}
}
}monitor_materialized_views 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.
Monitor materialized views status and freshness. 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 monitor_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.
monitor_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 monitor_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 monitor_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.
monitor_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.
Start from Postgres, 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.
239 Postgres tools catalogued and risk-classified — across an index of 43,000+ MCP servers.