列出已註冊資料來源(id、平台、取得策略、最後抓取時間)。
AI agents call list_sources to retrieve information from Healthcare OpenData MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists information about registered data sources and their metadata. It has no side effects, does not modify data, does not execute code or commands, and does not delete anything. It is purely informational/query-based, consistent with the 'Read' category.
From the tool's definition Tool name 'list_sources' and description '列出已註冊資料來源(id、平台、取得策略、最後抓取時間)' [list registered data sources (id, platform, acquisition strategy, last fetch time)] indicate retrieval of metadata about data sources without modification or execution.
Attacks that exploit this kind of access
列出已註冊資料來源(id、平台、取得策略、最後抓取時間)。. It is categorised as a Read tool in the Healthcare OpenData MCP MCP Server, which means it retrieves data without modifying state.
Register the Healthcare OpenData 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 Healthcare OpenData MCP. 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 Healthcare OpenData MCP server (trionnemesis/healthcare-opendata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →