list_generated_columns

A read tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg

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/io-github-devopam-mcpg/list-generated-columns.md

WHAT IT DOES

What list_generated_columns does on Mcpg

AI agents call list_generated_columns 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.

RISK

Why list_generated_columns is rated Low

The name clearly indicates this is a listing/querying operation that retrieves information about generated columns in PostgreSQL. There is no indication of modification, deletion, or execution of arbitrary code. Even though the description is empty, the semantic meaning of 'list' is unambiguous—it retrieves data.

From the tool's definition Tool name 'list_generated_columns' indicates a retrieval operation (list prefix) with no parameters shown. The verb 'list' is a standard Read category operation that queries database metadata without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_generated_columns 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 list_generated_columns, this is the rule to start with:

list_generated_columns Allowed

list_generated_columns 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": {
    "list_generated_columns": {}
  }
}

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

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

FAQ

Questions about list_generated_columns

What does the list_generated_columns tool do? +

list_generated_columns 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.

How do I enforce a policy on list_generated_columns? +

Register the Mcpg MCP server in PolicyLayer and add a rule for list_generated_columns: 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.

What risk level is list_generated_columns? +

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

Can I rate-limit list_generated_columns? +

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

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

list_generated_columns 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.

KEEP EXPLORING

More on Mcpg, and thousands of servers like it.

This server

All 252 Mcpg tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →