pg_regexp_match

Match text using POSIX regular expressions.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp

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-neverinfamous-postgres-mcp/pg-regexp-match.md

WHAT IT DOES

What pg_regexp_match does on PostgreSQL MCP Server

AI agents call pg_regexp_match to retrieve information from PostgreSQL MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why pg_regexp_match is rated Low

Regular expression matching is a read-only operation that examines text and returns matching results. It has no side effects on data—it does not create, modify, delete, or execute code. The severity is low because misuse would only affect which data is retrieved, not cause damage or unintended state changes.

From the tool's definition Tool name 'pg_regexp_match' and description 'Match text using POSIX regular expressions' indicate a query/pattern-matching operation that retrieves results without modifying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pg_regexp_match Allowed

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

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

FAQ

Questions about pg_regexp_match

What does the pg_regexp_match tool do? +

Match text using POSIX regular expressions. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pg_regexp_match? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_regexp_match: 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_regexp_match? +

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

Can I rate-limit pg_regexp_match? +

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

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

pg_regexp_match 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_regexp_match does on PostgreSQL MCP Server

Why pg_regexp_match is rated Low

The rule that runs pg_regexp_match safely

Questions about pg_regexp_match

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