跨資料集關鍵字搜尋(payload 全文 LIKE),回傳標註資料集的記錄(limit 上限 400)。
AI agents call search_records 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 queries data without modification, deletion, or execution of arbitrary code. It is a search function that returns healthcare data records matching keyword criteria. There are no side effects, irreversible actions, code execution, or financial implications. The blast radius is minimal—misuse would expose existing public healthcare data, which is the tool's intended purpose (open data access).
From the tool's definition Tool name is 'search_records' and description indicates it performs 'cross-dataset keyword search' (跨資料集關鍵字搜尋) using LIKE queries on payloads, returning records with dataset annotations and a limit of 400 results.
Attacks that exploit this kind of access
跨資料集關鍵字搜尋(payload 全文 LIKE),回傳標註資料集的記錄(limit 上限 400)。. 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 search_records: 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.
search_records 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 search_records 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 search_records. 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.
search_records 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 →