Get overview information about the connected database, including size, table count, and charset.
AI agents call get_database_info to retrieve information from Mcp Mysql Explorer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns informational properties about the database structure and configuration. It has no side effects, cannot modify data, and presents minimal risk even if misused by an AI agent—at worst, an agent learns non-sensitive structural information about a database it is already connected to.
From the tool's definition Tool retrieves database metadata (size, table count, charset) without modifying, deleting, or executing arbitrary operations. The verb 'Get' and the read-only nature of overview information classify this as a retrieval operation.
Attacks that exploit this kind of access
Get overview information about the connected database, including size, table count, and charset. It is categorised as a Read tool in the Mcp Mysql Explorer MCP Server, which means it retrieves data without modifying state.
Register the Mcp Mysql Explorer MCP server in PolicyLayer and add a rule for get_database_info: 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 Mcp Mysql Explorer. Nothing to install.
get_database_info 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 get_database_info 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 get_database_info. 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.
get_database_info is provided by the Mcp Mysql Explorer MCP server (xsg22/mcp-mysql-explorer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →