run_query
AI agents invoke run_query to trigger actions in Django Mcp Sql. 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.
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. SQL execution is a quintessential Execute category action. The empty description increases risk by hiding specifics about actual constraints.
From the tool's definition Tool named 'run_query' with empty description on a SQL-focused server that 'Provides a read-only PostgreSQL SQL surface.' The name 'run_query' indicates execution of arbitrary SQL statements.
Attacks that exploit this kind of access
run_query. It is categorised as a Execute tool in the Django Mcp Sql MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Django Mcp Sql MCP server in PolicyLayer and add a rule for run_query: 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 Django Mcp Sql. Nothing to install.
run_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_query 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.
Set action: deny in the PolicyLayer policy for run_query. 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.
run_query is provided by the Django Mcp Sql MCP server (thepapermen/django-mcp-sql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →