add_todo_to_plan · MCP MySQL App MCP: Risk & Policy

WHAT IT DOES

What add_todo_to_plan does on MCP MySQL App

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

WHY IT NEEDS A POLICY

Why add_todo_to_plan needs a policy

This tool creates or modifies data (adding a todo item to a plan) in a reversible manner. There is no deletion, financial impact, code execution, or irreversible data loss. The blast radius is minimal since a todo item in a plan can be removed or corrected. It qualifies as a Write operation per the classification rules.

From the tool's definition Tool description states it 'Add[s] a todo to a plan', which is a create/modify operation that adds a new item to an existing plan structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_todo_to_plan Rate-limited

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

FAQ

Questions about add_todo_to_plan

What does the add_todo_to_plan tool do? +

Add a todo to a plan, the todo is a step to do the plan. It is categorised as a Write tool in the MCP MySQL App MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_todo_to_plan? +

Register the MCP MySQL App MCP server in PolicyLayer and add a rule for add_todo_to_plan: 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 add_todo_to_plan? +

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

Can I rate-limit add_todo_to_plan? +

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

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

add_todo_to_plan 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.