AI agents invoke create_event to trigger actions in Mysql. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
MySQL scheduled events execute SQL code automatically at defined intervals or times. Creating a scheduled event sets up autonomous execution of arbitrary SQL, which can have wide-ranging effects on the database.
From the tool's definition "Create a scheduled event" - creates a scheduled event that will execute operations on a recurring or one-time basis in MySQL
Documented attack patterns abuse exactly the kind of access create_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql, and nothing reaches the server without passing your rules. This is the rule we recommend for create_event:
{
"version": "1",
"default": "deny",
"tools": {
"create_event": {
"limits": [
{
"counter": "create_event_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}create_event stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a scheduled event. It is categorised as a Execute tool in the Mysql MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mysql MCP server in PolicyLayer and add a rule for create_event: 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. Nothing to install.
create_event is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_event 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 create_event. 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.
create_event is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mysql, 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.
233 Mysql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.