# dataverse_list_tables

List all available tables in the Dataverse environment

Agent View of the PolicyLayer registry record for `dataverse_list_tables`. HTML page: https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-list-tables

## Facts

- Tool: `dataverse_list_tables`
- Server: Dataverse MCP Server (`ajscheuer/dataverse-mcp`) — https://policylayer.com/tools/ajscheuer-dataverse-mcp.md
- Homepage: https://github.com/Ajscheuer/dataverse-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, 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": "dataverse_list_tables",
    "arguments": {}
  }
}
```

## Why dataverse_list_tables is rated Low

This tool retrieves metadata about available tables without creating, modifying, deleting, or executing operations. It is a pure read operation with minimal blast radius—listing tables provides information but does not alter system state. Severity is low because unauthorized listing of table names presents an information disclosure risk but is not immediately actionable for data compromise without additional tools.

From the tool's own definition: "Tool name 'dataverse_list_tables' and description 'List all available tables in the Dataverse environment' indicate a retrieval operation with no side effects."

## Use case

AI agents call dataverse_list_tables to retrieve information from Dataverse 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 Dataverse MCP Server:

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

## Other tools on Dataverse MCP Server (5)

- `dataverse_delete_record` — Destructive — https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-delete-record.md
- `dataverse_query_records` — Read — https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-query-records.md
- `dataverse_read_record` — Read — https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-read-record.md
- `dataverse_create_record` — Write — https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-create-record.md
- `dataverse_update_record` — Write — https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-update-record.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=ajscheuer-dataverse-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ajscheuer-dataverse-mcp