Low Risk

regex_extract_all

Extract all pattern matches with capture groups using regex

How to control regex_extract_all ↓

What regex_extract_all does on Postgres Mcp Legacy

AI agents call regex_extract_all to retrieve information from Postgres Mcp Legacy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why regex_extract_all needs a policy

This tool performs pattern matching and extraction on existing data (likely database query results or strings), returning matches without side effects. It is a data retrieval/transformation operation with no capability to modify, delete, or execute commands. The low severity reflects minimal blast radius—regex extraction on queried data poses no risk of data loss, financial impact, or unintended execution.

From the tool's definition Tool name 'regex_extract_all' and description 'Extract all pattern matches with capture groups using regex' indicate a read-only operation that processes and returns data without modifying, deleting, or executing external operations.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access regex_extract_all gives an agent:

How to control regex_extract_all

PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres Mcp Legacy, and nothing reaches the server without passing your rules. This is the rule we recommend for regex_extract_all:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "regex_extract_all": {}
  }
}

regex_extract_all is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Postgres Mcp Legacy — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about regex_extract_all

What does the regex_extract_all tool do? +

Extract all pattern matches with capture groups using regex. It is categorised as a Read tool in the Postgres Mcp Legacy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on regex_extract_all? +

Register the Postgres Mcp Legacy MCP server in PolicyLayer and add a rule for regex_extract_all: 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 Postgres Mcp Legacy. Nothing to install.

What risk level is regex_extract_all? +

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

Can I rate-limit regex_extract_all? +

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

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

regex_extract_all is provided by the Postgres Mcp Legacy MCP server (neverinfamous/postgres-mcp-legacy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Postgres Mcp Legacy tool call.

Start from Postgres Mcp Legacy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

60 Postgres Mcp Legacy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.