List triggers defined on a table.
AI agents call mysql_show_table_triggers to retrieve information from Mysql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about triggers on a table without modifying, executing, or deleting anything. It is a straightforward information-gathering operation. The low severity reflects that trigger metadata exposure poses minimal risk to system integrity, though it could inform privilege escalation in some scenarios.
From the tool's definition Tool name 'mysql_show_table_triggers' and description 'List triggers defined on a table' indicate a query/retrieval operation with no side effects. The verb 'show/list' and the server's stated purpose of 'read-only queries' confirm this is inspection only.
Documented attack patterns abuse exactly the kind of access mysql_show_table_triggers 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 mysql_show_table_triggers:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_show_table_triggers": {}
}
}mysql_show_table_triggers 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.
List triggers defined on a table. It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_show_table_triggers: 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.
mysql_show_table_triggers 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 mysql_show_table_triggers 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 mysql_show_table_triggers. 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.
mysql_show_table_triggers 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.