enable_extension

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/enable-extension.md

WHAT IT DOES

What enable_extension does on Mcpg

AI agents invoke enable_extension 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 enable_extension is rated High

Enabling a PostgreSQL extension modifies the database system configuration by loading and activating extension code within the database. This is an Execute-level action as it triggers external operations and can load untrusted code or alter database behavior.

From the tool's definition Tool name 'enable_extension' on a production-grade PostgreSQL MCP server; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

enable_extension Rate-limited

enable_extension 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": {
    "enable_extension": {
      "limits": [
        {
          "counter": "enable_extension_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 enable_extension call is checked against it from then on.

FAQ

Questions about enable_extension

What does the enable_extension tool do? +

enable_extension 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 enable_extension? +

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

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

Can I rate-limit enable_extension? +

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

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

enable_extension 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

All high-risk MCP tools → The MCP Attack Database →

Guides

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