mysql_vector_info
List all vector columns for a table and their dimensions.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-vector-info.md
What mysql_vector_info does on Mysql Mcp
AI agents call mysql_vector_info to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mysql_vector_info is rated Low
The tool performs a read-only query to retrieve information about vector columns and their properties. It has no side effects, does not execute code, does not modify data, and does not delete or create resources. This is a straightforward metadata retrieval operation typical of Read category tools.
From the tool's definition Tool name and description indicate a 'List' operation: 'List all vector columns for a table and their dimensions.' This retrieves metadata about vector columns without modifying, executing, or deleting data.
Attacks that exploit this kind of access
The rule that runs mysql_vector_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_vector_info, this is the rule to start with:
mysql_vector_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_vector_info call is checked against it from then on.
Questions about mysql_vector_info
List all vector columns for a table and their dimensions. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_vector_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. Nothing to install.
mysql_vector_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 mysql_vector_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 mysql_vector_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.
mysql_vector_info is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mysql, and thousands of servers like it.
This server
Across the catalogue