list_sources
A read tool on the 311 Analytics Agent MCP server.
This record as markdown: /tools/311-analytics-agent/list-sources.md
What list_sources does on 311 Analytics Agent
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.
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 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…
Attacks that exploit this kind of access
The rule that runs list_sources safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 311 Analytics Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_sources, this is the rule to start with:
list_sources is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 311 Analytics Agent, apply this rule, and every list_sources call is checked against it from then on.
Questions about list_sources
list_sources is a read tool on the 311 Analytics Agent MCP server. It is categorised as a Read tool in the 311 Analytics Agent MCP Server, which means it retrieves data without modifying state.
Register the 311 Analytics Agent MCP server in PolicyLayer and add a rule for list_sources: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches 311 Analytics Agent. Nothing to install.
list_sources is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_sources rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_sources. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_sources is provided by the 311 Analytics Agent MCP server (chenziliang1/311-analytics-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 311 Analytics Agent, and thousands of servers like it.
This server
Across the catalogue