wellness__check_telehealth_eligibility
［數位健康與遠距醫療指南］台灣通訊診察（視訊、電話看診）資格：113-07-01 起 11 種特殊情形、可否開處方、流程。situation 可用：remote(山地、離島、偏僻地區)、acute_post(急性後期照護)、chronic_plan(慢性病照護計畫收案病人)、ltc(長期照顧服務對象)、family_doc(家庭醫師收治照護)、home_care(居家醫療照護)、terminal(疾病末期照護)、mobility(行動不便照護)、prison(矯正機關收容照護)、disaster(災害、傳染病或其他重大變故照護)、intl(國際醫療照護)；不填則列出全部。
This record as markdown: /tools/com-penguindriver-hub/wellness--check-telehealth-eligibility.md
What wellness__check_telehealth_eligibility does on AI 代理人任務中樞
AI agents call wellness__check_telehealth_eligibility to retrieve information from AI 代理人任務中樞 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
situation | string | — |
Parameters from the server's own tool schema.
Why wellness__check_telehealth_eligibility is rated Low
Even though wellness__check_telehealth_eligibility only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs wellness__check_telehealth_eligibility safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AI 代理人任務中樞, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wellness__check_telehealth_eligibility, this is the rule to start with:
wellness__check_telehealth_eligibility 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 AI 代理人任務中樞, apply this rule, and every wellness__check_telehealth_eligibility call is checked against it from then on.
Questions about wellness__check_telehealth_eligibility
［數位健康與遠距醫療指南］台灣通訊診察（視訊、電話看診）資格：113-07-01 起 11 種特殊情形、可否開處方、流程。situation 可用：remote(山地、離島、偏僻地區)、acute_post(急性後期照護)、chronic_plan(慢性病照護計畫收案病人)、ltc(長期照顧服務對象)、family_doc(家庭醫師收治照護)、home_care(居家醫療照護)、terminal(疾病末期照護)、mobility(行動不便照護)、prison(矯正機關收容照護)、disaster(災害、傳染病或其他重大變故照護)、intl(國際醫療照護)；不填則列出全部。. It is categorised as a Read tool in the AI 代理人任務中樞 MCP Server, which means it retrieves data without modifying state.
wellness__check_telehealth_eligibility accepts 1 parameter: situation. The full parameter table on this page comes from the server's own tool schema.
Register the AI 代理人任務中樞 MCP server in PolicyLayer and add a rule for wellness__check_telehealth_eligibility: 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 AI 代理人任務中樞. Nothing to install.
wellness__check_telehealth_eligibility 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 wellness__check_telehealth_eligibility 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 wellness__check_telehealth_eligibility. 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.
wellness__check_telehealth_eligibility is provided by the AI 代理人任務中樞 MCP server (https://hub.penguindriver.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AI 代理人任務中樞, and thousands of servers like it.
This server
Across the catalogue