get_schema_info
Get column metadata for a table or all tables in the configured database:
This record as markdown: /tools/designcomputer-mysql-mcp-server/get-schema-info.md
What get_schema_info does on MySQL MCP Server
AI agents call get_schema_info to retrieve information from MySQL MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_schema_info is rated Low
This tool retrieves structural metadata (column names, types, constraints) about database tables. It performs no write operations, executes no queries against data, and has no side effects. The action is informational only, consistent with the Read category. Severity is low because schema information is typically non-sensitive structural data, and misuse would not result in data loss or unintended modifications.
From the tool's definition Tool name 'get_schema_info' and description 'Get column metadata for a table or all tables' indicate pure retrieval of schema information with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_schema_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MySQL MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_schema_info, this is the rule to start with:
get_schema_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 Server, apply this rule, and every get_schema_info call is checked against it from then on.
Questions about get_schema_info
Get column metadata for a table or all tables in the configured database:. 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_schema_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_schema_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_schema_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_schema_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_schema_info is provided by the MySQL MCP Server MCP server (designcomputer/mysql_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MySQL MCP Server, and thousands of servers like it.
This server
Across the catalogue