list_pg_search_indexes

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-pg-search-indexes.md

WHAT IT DOES

What list_pg_search_indexes does on Mcpg

AI agents call list_pg_search_indexes 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_pg_search_indexes is rated Low

The tool name clearly follows the 'list_*' pattern, which in standard API conventions denotes a read operation that retrieves and returns data without modification or side effects. Even without a description, this is a reliable indicator of Read category. The severity is low because listing indexes is informational and carries no risk of data loss or unauthorized modification.

From the tool's definition Tool name 'list_pg_search_indexes' indicates a listing/retrieval operation. The 'list_' prefix is a strong signal of read-only query functionality.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_pg_search_indexes Allowed

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

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_pg_search_indexes call is checked against it from then on.

FAQ

Questions about list_pg_search_indexes

What does the list_pg_search_indexes tool do? +

list_pg_search_indexes 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_pg_search_indexes? +

Register the Mcpg MCP server in PolicyLayer and add a rule for list_pg_search_indexes: 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_pg_search_indexes? +

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

Can I rate-limit list_pg_search_indexes? +

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

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

list_pg_search_indexes 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

search_torrents on M-Team MCP Server →aiva_list_affiliates on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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