pg_search_run

A execute tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-devopam-mcpg/pg-search-run.md

WHAT IT DOES

What pg_search_run does on Mcpg

AI agents invoke pg_search_run to trigger actions in Mcpg. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why pg_search_run is rated High

The name 'pg_search_run' implies running/executing a search query against a PostgreSQL database. The 'run' suffix strongly suggests execution semantics. Given the PostgreSQL context and sibling tools that involve query analysis, this likely executes database queries. With no description, confidence is reduced, but 'run' in context of a DB server typically means Execute.

From the tool's definition Tool name 'pg_search_run' suggests execution of a search operation against PostgreSQL; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pg_search_run Rate-limited

pg_search_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pg_search_run": {
      "limits": [
        {
          "counter": "pg_search_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about pg_search_run

What does the pg_search_run tool do? +

pg_search_run is a execute tool on the Mcpg MCP server. It is categorised as a Execute tool in the Mcpg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pg_search_run? +

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

pg_search_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pg_search_run? +

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

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

pg_search_run 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 → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →