AI agents call get_operation_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 operation logs. It is a read-only retrieval operation with no side effects, no code execution, and no data modification. The low severity reflects minimal risk: logs are typically informational records, and accessing them does not affect system state or data integrity. Confidence is high because the intent is unambiguous from both name and description.
From the tool's definition Tool name is 'get_operation_logs' and description states 'Get operation logs' — this retrieves historical log data without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_operation_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_operation_logs:
{
"version": "1",
"default": "deny",
"tools": {
"get_operation_logs": {}
}
}get_operation_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 operation logs. 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_operation_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_operation_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_operation_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_operation_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_operation_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.