generate_synthetic_data · SingleStore MCP Server MCP

WHAT IT DOES

What generate_synthetic_data does on SingleStore MCP Server

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

WHY IT NEEDS A POLICY

Why generate_synthetic_data needs a policy

Generating synthetic data involves inserting or populating a table with new records, making this a Write operation. It is reversible (generated data can be deleted), so it does not qualify as Destructive. While not as severe as Financial or Destructive, misuse could create unwanted data pollution, corrupt analytics, or cause storage bloat—hence medium severity.

From the tool's definition Tool description states 'Generate synthetic data for a table' which creates new data within a table. The verb 'generate' combined with 'for a table' indicates data creation/insertion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_synthetic_data Rate-limited

generate_synthetic_data 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": {
    "generate_synthetic_data": {
      "limits": [
        {
          "counter": "generate_synthetic_data_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 SingleStore MCP Server, so you can run agents against it safely.

FAQ

Questions about generate_synthetic_data

What does the generate_synthetic_data tool do? +

Generate synthetic data for a table. It is categorised as a Write tool in the SingleStore 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 generate_synthetic_data? +

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

What risk level is generate_synthetic_data? +

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

Can I rate-limit generate_synthetic_data? +

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

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

generate_synthetic_data is provided by the SingleStore MCP Server MCP server (madhukarkumar/singlestore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.