# list_sources

A read tool on the 311 Analytics Agent MCP server.

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

## Facts

- Tool: `list_sources`
- Server: 311 Analytics Agent (`chenziliang1/311-analytics-agent`) — https://policylayer.com/tools/311-analytics-agent.md
- Homepage: https://github.com/chenziliang1/311-analytics-agent
- Risk category: Read (Low risk)
- Registry record: grade A, 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": "list_sources",
    "arguments": {}
  }
}
```

## Why list_sources is rated Low

The naming pattern and sibling tools (all Read operations) strongly suggest this is a data retrieval function that lists searchable sources. No description is provided, which lowers confidence slightly, but the tool name and server purpose make it clear this is a Read operation with minimal risk. A user or agent gaining access to source listings poses no significant security threat.

From the tool's own definition: "Tool name 'list_sources' indicates a query/enumeration operation. Given the server context of a search MCP with tools like 'search', 'fetch_content', and 'read_url', this tool almost certainly retrieves or enumerates available data sources without modifying…"

## Use case

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

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

## Other tools on 311 Analytics Agent (4)

- `read_source` — Read — https://policylayer.com/tools/311-analytics-agent/read-source.md
- `record_feedback` — Read — https://policylayer.com/tools/311-analytics-agent/record-feedback.md
- `visualize` — Read — https://policylayer.com/tools/311-analytics-agent/visualize.md
- `warehouse_query` — Read — https://policylayer.com/tools/311-analytics-agent/warehouse-query.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=311-analytics-agent · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/311-analytics-agent
