列出可查詢的資料集(id、標題、collection、欄位名)。
AI agents call list_datasets 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 metadata about available datasets without modifying, executing operations on, or deleting data. It enables discovery of what datasets exist and their structure, which is a Read category operation. The low severity reflects minimal risk—listing dataset metadata cannot harm systems or data even if misused by an agent.
From the tool's definition Tool name is 'list_datasets' and description states it '列出可查詢的資料集(id、標題、collection、欄位名)' which translates to 'list queryable datasets (id, title, collection, field names)'. This is a retrieval/listing operation with no side effects.
Attacks that exploit this kind of access
列出可查詢的資料集(id、標題、collection、欄位名)。. 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_datasets: 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_datasets 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_datasets 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_datasets. 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_datasets 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 →