AI agents call get_ddl_sql_logs to retrieve information from MCP MySQL Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing DDL operation logs for auditing or review purposes. It has no side effects—it does not execute SQL, modify data, delete records, or trigger external operations. The severity is low because accessing logs poses minimal risk to system integrity, though log access should still be appropriately controlled.
From the tool's definition Tool name 'get_ddl_sql_logs' and description 'Get DDL SQL operation logs' indicate this retrieves historical log records. The verb 'Get' and noun 'logs' are explicit read operations with no modification or execution of actual database changes.
Documented attack patterns abuse exactly the kind of access get_ddl_sql_logs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP MySQL Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_ddl_sql_logs:
{
"version": "1",
"default": "deny",
"tools": {
"get_ddl_sql_logs": {}
}
}get_ddl_sql_logs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get DDL SQL operation logs (v2.0.1+). It is categorised as a Read tool in the MCP MySQL Server MCP Server, which means it retrieves data without modifying state.
Register the MCP MySQL Server MCP server in PolicyLayer and add a rule for get_ddl_sql_logs: 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 Server. Nothing to install.
get_ddl_sql_logs 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_ddl_sql_logs 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_ddl_sql_logs. 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_ddl_sql_logs is provided by the MCP MySQL Server MCP server (liliangshan/mcp-server-mysql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP MySQL Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 MCP MySQL Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.