# get_table_sample

Fetch a small sample of rows from a table to understand its data format and content.

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

## Facts

- Tool: `get_table_sample`
- 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_table_sample",
    "arguments": {}
  }
}
```

## Why get_table_sample is rated Low

This tool retrieves a limited subset of data for inspection purposes only. There is no capability to modify, delete, or execute operations. The 'small sample' constraint further limits data exposure. Even if misused by an AI agent, the worst outcome is unauthorized data reading, which carries lower risk than write, execute, or destructive operations.

From the tool's own definition: "Tool name 'get_table_sample' and description explicitly states 'Fetch a small sample of rows from a table' — a retrieval operation with no modification or side effects. The server description confirms it enables 'read data' as a core function."

## Use case

AI agents call get_table_sample 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_table_sample": {}
  }
}
```

## Other tools on MySQL MCP Server (2)

- `execute_sql` — Execute — https://policylayer.com/tools/designcomputer-mysql-mcp-server/execute-sql.md
- `get_schema_info` — Read — https://policylayer.com/tools/designcomputer-mysql-mcp-server/get-schema-info.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