# execute

Execute a write SQL statement (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, etc.) against the PostgreSQL database.

Agent View of the PolicyLayer registry record for `execute`. HTML page: https://policylayer.com/tools/aeiyannn-postgree-mcp/execute

## Facts

- Tool: `execute`
- Server: PostgreSQL MCP Server (`aeiyannn/postgree-mcp`) — https://policylayer.com/tools/aeiyannn-postgree-mcp.md
- Homepage: https://github.com/aeiyannn/postgree-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "execute",
    "arguments": {}
  }
}
```

## Why execute is rated Critical

This tool explicitly supports DROP, DELETE, and ALTER operations among others, which can irreversibly destroy or overwrite data and schema structures. Since it permits the most severe destructive SQL operations (DROP, DELETE) alongside write operations, it must be classified as Destructive.

From the tool's own definition: "Execute a write SQL statement (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, etc.) against the PostgreSQL database."

## Use case

AI agents call execute to permanently remove resources in PostgreSQL MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches PostgreSQL MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "execute"
  ]
}
```

## Other tools on PostgreSQL MCP Server (4)

- `describe_table` — Read — https://policylayer.com/tools/aeiyannn-postgree-mcp/describe-table.md
- `list_schemas` — Read — https://policylayer.com/tools/aeiyannn-postgree-mcp/list-schemas.md
- `list_tables` — Read — https://policylayer.com/tools/aeiyannn-postgree-mcp/list-tables.md
- `query` — Read — https://policylayer.com/tools/aeiyannn-postgree-mcp/query.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=aeiyannn-postgree-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/aeiyannn-postgree-mcp