Get detailed status information about tables
AI agents call mysql_table_status to retrieve information from Multi-Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about database tables, which is a read-only operation with no side effects. It does not create, modify, delete, or execute code. The sibling tools on the server include destructive operations (delete_many, delete_one, drop_index) and write operations (insert_many, insert_one, create_index), but this specific tool is clearly informational.
From the tool's definition Tool name 'mysql_table_status' and description 'Get detailed status information about tables' indicate a query operation that retrieves metadata about table structure and state without modifying data.
Attacks that exploit this kind of access
Get detailed status information about tables. It is categorised as a Read tool in the Multi-Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-Database MCP Server MCP server in PolicyLayer and add a rule for mysql_table_status: 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 Multi-Database MCP Server. Nothing to install.
mysql_table_status 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_table_status 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_table_status. 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_table_status is provided by the Multi-Database MCP Server MCP server (nam088/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
mysql_table_status is one line of Multi-Database MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →