This record as markdown: /tools/io-github-devopam-mcpg/get-pg19-ddl-status.md
What get_pg19_ddl_status does on Mcpg
AI agents call get_pg19_ddl_status to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_pg19_ddl_status is rated Low
This tool appears to retrieve or query the current status of PostgreSQL 19 DDL operations. Read operations that query system state without side effects fall into the Read category. The low severity reflects that status queries cannot modify, delete, or execute code—they only retrieve information.
From the tool's definition Tool name 'get_pg19_ddl_status' indicates a status-retrieval operation. The 'get_' prefix and 'status' suffix suggest read-only querying of DDL (Data Definition Language) state.
Attacks that exploit this kind of access
The rule that runs get_pg19_ddl_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_pg19_ddl_status, this is the rule to start with:
get_pg19_ddl_status 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 Mcpg, apply this rule, and every get_pg19_ddl_status call is checked against it from then on.
Questions about get_pg19_ddl_status
get_pg19_ddl_status is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.
Register the Mcpg MCP server in PolicyLayer and add a rule for get_pg19_ddl_status: 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 Mcpg. Nothing to install.
get_pg19_ddl_status 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_pg19_ddl_status 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_pg19_ddl_status. 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_pg19_ddl_status is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue