do_todo · MCP MySQL App MCP: Risk & Policy

WHAT IT DOES

What do_todo does on MCP MySQL App

AI agents invoke do_todo to trigger actions in MCP MySQL App. 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 do_todo needs a policy

The description is nearly empty, providing no detail about what 'doing a todo' entails. However, given the server context (MySQL database interaction, SQL query execution) and sibling tools like 'sql_query' and 'report_todo', executing a todo likely triggers some database operation or external action.

From the tool's definition Tool name 'do_todo' and description 'Do a todo' are uninformative about what action is actually performed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

do_todo Rate-limited

do_todo 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": {
    "do_todo": {
      "limits": [
        {
          "counter": "do_todo_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 MCP MySQL App, so you can run agents against it safely.

FAQ

Questions about do_todo

What does the do_todo tool do? +

Do a todo. It is categorised as a Execute tool in the MCP MySQL App MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on do_todo? +

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

What risk level is do_todo? +

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

Can I rate-limit do_todo? +

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

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

do_todo is provided by the MCP MySQL App MCP server (zalab-inc/mcp-mysql-app). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.