get_db_info
AI agents call get_db_info to retrieve information from MySQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves database information (schema, structure, metadata) with no side effects. The server explicitly restricts access to read-only operations. Confidence is slightly reduced (0.85 vs 0.95) because the tool description is empty, preventing direct evidence from the tool's own documentation, but the server context and sibling tools provide strong contextual support for classification as a Read operation…
From the tool's definition Server is explicitly described as 'read-only access' with capabilities limited to 'SELECT queries, table structure inspection, and database schema exploration.' Tool name 'get_db_info' and its placement among sibling tools (get_table_structure, list_tables,…
Attacks that exploit this kind of access
get_db_info. It is categorised as a Read tool in the MySQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for get_db_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 MySQL MCP Server. Nothing to install.
get_db_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_db_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_db_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_db_info is provided by the MySQL MCP Server MCP server (jeweis/jewei-mysql-mcp-server). 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 →