create_job · MindsDB MySQL MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_job does on MindsDB MySQL MCP Server

AI agents invoke create_job to trigger actions in MindsDB MySQL MCP Server. 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.

WHY IT NEEDS A POLICY

Why create_job needs a policy

This tool schedules recurring SQL query execution, which constitutes an ongoing Execute action. It can trigger repeated data modifications, deletions, or other operations at scale. The blast radius is high because a misconfigured job could repeatedly execute harmful queries automatically without further user intervention.

From the tool's definition Create a scheduled job to run a query at regular intervals

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_job Rate-limited

create_job stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_job": {
      "limits": [
        {
          "counter": "create_job_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about create_job

What does the create_job tool do? +

Create a scheduled job to run a query at regular intervals. It is categorised as a Execute tool in the MindsDB MySQL MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_job? +

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

What risk level is create_job? +

create_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_job? +

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

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

create_job is provided by the MindsDB MySQL MCP Server MCP server (nikhgupta/mindsdb-mysql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.