mysql_event_list

List all scheduled events with status, schedule, and execution 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-event-list.md

WHAT IT DOES

What mysql_event_list does on Mysql Mcp

AI agents call mysql_event_list 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_event_list is rated Low

This tool retrieves information about scheduled MySQL events (status, schedule, execution details) with no side effects. It is purely observational/informational, matching the Read category definition of 'retrieves or queries data; no side effects'.

From the tool's definition Tool name 'mysql_event_list' and description 'List all scheduled events with status, schedule, and execution info' indicate a read-only query operation that retrieves and displays event metadata without modifying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_event_list 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_event_list, this is the rule to start with:

mysql_event_list Allowed

mysql_event_list 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_event_list": {}
  }
}

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_event_list call is checked against it from then on.

FAQ

Questions about mysql_event_list

What does the mysql_event_list tool do? +

List all scheduled events with status, schedule, and execution 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_event_list? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_event_list: 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_event_list? +

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

Can I rate-limit mysql_event_list? +

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

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

mysql_event_list 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 →get_event_details on CTFtime MCP Server → The MCP Attack Database →

Guides

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