# list_sources

Datasets this API serves, with the tool name and filter params for each. Free to call.

Agent View of the PolicyLayer registry record for `list_sources`. HTML page: https://policylayer.com/tools/com-gankdat-gankdat/list-sources

## Facts

- Tool: `list_sources`
- Server: Gankdat (`https://gankdat.com/mcp`) — https://policylayer.com/tools/com-gankdat-gankdat.md
- Homepage: https://github.com/https://gankdat.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- 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": "list_sources",
    "arguments": {}
  }
}
```

## Why list_sources is rated Low

This tool retrieves informational metadata about available datasets and their parameters. It is purely read-only, has no side effects, does not execute code or commands, and does not modify or delete data. The phrase 'Free to call' further reinforces that it is a safe informational endpoint. No blast radius from misuse.

From the tool's own definition: "Tool name 'list_sources' and description 'Datasets this API serves, with the tool name and filter params for each. Free to call.' indicate a retrieval/query operation that returns metadata about available data sources with no modification or side effects."

## Use case

AI agents call list_sources to retrieve information from Gankdat 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 Gankdat:

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

## Other tools on Gankdat (8)

- `get_usage` — Read — https://policylayer.com/tools/com-gankdat-gankdat/get-usage.md
- `query_eu_ted` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-eu-ted.md
- `query_sam_exclusions` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-sam-exclusions.md
- `query_uk_companies` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-uk-companies.md
- `query_uk_insolvency` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-uk-insolvency.md
- `query_uk_planning` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-uk-planning.md
- `query_uk_sanctions` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-uk-sanctions.md
- `query_uk_tenders` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-uk-tenders.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=com-gankdat-gankdat · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gankdat-gankdat