pg_cron_create_extension

Enable the pg_cron extension for job scheduling. Requires superuser privileges.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp

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-neverinfamous-postgres-mcp/pg-cron-create-extension.md

WHAT IT DOES

What pg_cron_create_extension does on PostgreSQL MCP Server

AI agents invoke pg_cron_create_extension to trigger actions in PostgreSQL MCP Server. 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_cron_create_extension is rated High

Enabling a PostgreSQL extension modifies the database environment and activates job scheduling capabilities. This is an irreversible-adjacent system-level operation that requires superuser privileges, enabling execution of scheduled jobs within the database. It falls under Execute because it triggers external/system-level operations and alters the database's runtime capabilities, rather than simply writing data.

From the tool's definition 'Enable the pg_cron extension for job scheduling. Requires superuser privileges.'

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_cron_create_extension safely

PolicyLayer is an MCP gateway: it sits between your AI agents and PostgreSQL MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pg_cron_create_extension, this is the rule to start with:

pg_cron_create_extension Rate-limited

pg_cron_create_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": {
    "pg_cron_create_extension": {
      "limits": [
        {
          "counter": "pg_cron_create_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 PostgreSQL MCP Server, apply this rule, and every pg_cron_create_extension call is checked against it from then on.

FAQ

Questions about pg_cron_create_extension

What does the pg_cron_create_extension tool do? +

Enable the pg_cron extension for job scheduling. Requires superuser privileges. It is categorised as a Execute tool in the PostgreSQL MCP Server 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_cron_create_extension? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_cron_create_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 PostgreSQL MCP Server. Nothing to install.

What risk level is pg_cron_create_extension? +

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

Can I rate-limit pg_cron_create_extension? +

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

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

pg_cron_create_extension is provided by the PostgreSQL MCP Server MCP server (@neverinfamous/postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What pg_cron_create_extension does on PostgreSQL MCP Server

Why pg_cron_create_extension is rated High

The rule that runs pg_cron_create_extension safely

Questions about pg_cron_create_extension

More on PostgreSQL MCP Server, and thousands of servers like it.