Get a plan with detailed information with uncertainty list and todo list
AI agents call get_detailed_plan to retrieve information from MCP MySQL App without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing plan data (detailed information, uncertainty list, todo list) and returns it to the user. There are no side effects, no data modification, no code execution, and no destructive operations. It is a straightforward Read operation with low severity because it simply fetches information that is already stored in the system.
From the tool's definition Tool name 'get_detailed_plan' and description 'Get a plan with detailed information with uncertainty list and todo list' indicate a retrieval operation that queries and returns plan data without modifying it.
Attacks that exploit this kind of access
Get a plan with detailed information with uncertainty list and todo list. It is categorised as a Read tool in the MCP MySQL App MCP Server, which means it retrieves data without modifying state.
Register the MCP MySQL App MCP server in PolicyLayer and add a rule for get_detailed_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.
get_detailed_plan is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_detailed_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.
Set action: deny in the PolicyLayer policy for get_detailed_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.
get_detailed_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →