mysql_list_events

List all scheduled events with execution status and schedule info.

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-list-events.md

WHAT IT DOES

What mysql_list_events does on Mysql Mcp

AI agents call mysql_list_events to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why mysql_list_events is rated Low

This tool retrieves information about scheduled events in MySQL, displaying their status and schedule details. It is a non-destructive read-only operation that does not modify, delete, or execute any database changes. The blast radius of misuse is minimal—an attacker gains visibility into scheduled events but cannot alter or delete them through this tool alone.

From the tool's definition Tool name 'mysql_list_events' and description 'List all scheduled events with execution status and schedule info' indicate a query/retrieval operation with no data modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_list_events safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_list_events, this is the rule to start with:

mysql_list_events Allowed

mysql_list_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_list_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_list_events call is checked against it from then on.

FAQ

Questions about mysql_list_events

What does the mysql_list_events tool do? +

List all scheduled events with execution status and schedule info. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_list_events? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_list_events: 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 Mysql Mcp. Nothing to install.

What risk level is mysql_list_events? +

mysql_list_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mysql_list_events? +

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

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

mysql_list_events is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mysql, and thousands of servers like it.

This server

All 223 Mysql tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →