df_generate_sql · DataForge Semantic MCP Server MCP

WHAT IT DOES

What df_generate_sql does on DataForge Semantic MCP Server

AI agents use df_generate_sql to create or update resources in DataForge Semantic MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DataForge Semantic MCP Server environment.

WHY IT NEEDS A POLICY

Why df_generate_sql needs a policy

This tool creates SQL code as output rather than merely reading data. While the tool itself does not execute the SQL (which would make it Execute), it produces executable code artifacts. The 'read-only, not executed' qualifier reduces severity from high to medium, as the direct blast radius depends on how the generated SQL is used downstream.

From the tool's definition The tool description states it 'Generate[s] SQL script for a data mart' — generating code that can be executed by downstream systems constitutes creating/modifying artifacts.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

df_generate_sql Rate-limited

df_generate_sql stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "df_generate_sql": {
      "limits": [
        {
          "counter": "df_generate_sql_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DataForge Semantic MCP Server, so you can run agents against it safely.

FAQ

Questions about df_generate_sql

What does the df_generate_sql tool do? +

Generate SQL script for a data mart (read-only, not executed). It is categorised as a Write tool in the DataForge Semantic MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on df_generate_sql? +

Register the DataForge Semantic MCP Server MCP server in PolicyLayer and add a rule for df_generate_sql: 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 DataForge Semantic MCP Server. Nothing to install.

What risk level is df_generate_sql? +

df_generate_sql is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit df_generate_sql? +

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

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

df_generate_sql is provided by the DataForge Semantic MCP Server MCP server (sgromych/dataforge-mcp-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.