improve_plan · MCP MySQL App MCP: Risk & Policy

WHAT IT DOES

What improve_plan does on MCP MySQL App

AI agents use improve_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 improve_plan needs a policy

This tool modifies plan data (updates/improves plans) without deleting them or executing arbitrary operations. It falls under the Write category since it creates or modifies data reversibly. Severity is medium because unintended plan modifications could disrupt user workflows, but the impact is localized to plan records and reversible.

From the tool's definition Tool description states 'Make sure the plan is improved after the uncertainty is resolved', indicating modification of existing plan data. Sibling tools include 'create_plan' and 'get_detailed_plan', establishing that this server manages plan entities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

improve_plan Rate-limited

improve_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": {
    "improve_plan": {
      "limits": [
        {
          "counter": "improve_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 improve_plan

What does the improve_plan tool do? +

Make sure the plan is improved after the uncertainty is resolved. 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 improve_plan? +

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

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

Can I rate-limit improve_plan? +

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

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

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