// SCAN REPORT

Django Mcp Sql

3 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

1 can modify or destroy data

2 read-only

3 tools total

Community server · catalogue entry verified 02/07/2026

How to control Django Mcp Sql ↓

TOOL MAP

What Django Mcp Sql exposes to your agents

Read (2) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Django Mcp Sql tools

Execute · High run_query Although the server is advertised as read-only with 'defense-in-depth security layers,' the 'run_query' tool executes SQL commands whose behavior depends entirely on the query content provided by the agent.

1 of Django Mcp Sql's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Django Mcp Sql

PolicyLayer is an MCP gateway — it sits between your AI agents and Django Mcp Sql, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "describe_table": {
    "limits": [
      {
        "counter": "describe_table_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Django Mcp Sql — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON DJANGO MCP SQL →

Instant setup, no code required.

FULL CATALOGUE

All 3 Django Mcp Sql tools

EXECUTE 1 tools

Execute run_query run_query

READ 2 tools

Read describe_table Return column definitions for a whitelisted table. Read list_tables list_tables

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Django Mcp Sql

Is the Django Mcp Sql MCP server safe to use without restrictions? +

The Django Mcp Sql server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Django Mcp Sql MCP server expose? +

3 tools across 2 categories: Execute, Read. 2 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Django Mcp Sql? +

Register the Django Mcp Sql MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Django Mcp Sql tool call.

Deterministic rules across all 3 Django Mcp Sql tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DJANGO MCP SQL →

Instant setup, no code required.

3 Django Mcp Sql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Django Mcp Sql's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →