# get_schema_info

Get column metadata for a table or all tables in the configured database:

Agent View of the PolicyLayer registry record for `get_schema_info`. HTML page: https://policylayer.com/tools/designcomputer-mysql-mcp-server/get-schema-info

## Facts

- Tool: `get_schema_info`
- Server: MySQL MCP Server (`designcomputer/mysql_mcp_server`) — https://policylayer.com/tools/designcomputer-mysql-mcp-server.md
- Homepage: https://github.com/designcomputer/mysql_mcp_server
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_schema_info",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MySQL MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_schema_info": {}
  }
}
```

## Other tools on MySQL MCP Server (2)

- `execute_sql` — Execute — https://policylayer.com/tools/designcomputer-mysql-mcp-server/execute-sql.md
- `get_table_sample` — Read — https://policylayer.com/tools/designcomputer-mysql-mcp-server/get-table-sample.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=designcomputer-mysql-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/designcomputer-mysql-mcp-server