translate-batch · Sql2odata MCP: Risk & Policy

WHAT IT DOES

What translate-batch does on Sql2odata

AI agents invoke translate-batch to trigger actions in Sql2odata. 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 translate-batch needs a policy

The tool translates SQL including INSERT, UPDATE, and DELETE into OData v4 requests. While it may only perform translation (Read), the server description indicates it 'enables users to convert complex SQL queries into OData-compliant requests' which implies execution of those requests.

From the tool's definition Translate multiple SQL statements into OData v4 at once. Supporting SELECT, INSERT, UPDATE, and DELETE operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

translate-batch Rate-limited

translate-batch 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": {
    "translate-batch": {
      "limits": [
        {
          "counter": "translate-batch_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 Sql2odata, so you can run agents against it safely.

FAQ

Questions about translate-batch

What does the translate-batch tool do? +

Translate multiple SQL statements into OData v4 at once. Returns all results in a single response. It is categorised as a Execute tool in the Sql2odata MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on translate-batch? +

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

What risk level is translate-batch? +

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

Can I rate-limit translate-batch? +

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

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

translate-batch is provided by the Sql2odata MCP server (moonraker46/sql2odata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.