list_diseases

Every tracked affliction and its current phase (incubating / active / recovering / recovered / fatal).

SERVERTorch-to-Crown SOURCEDiogenes187/Torch-to-Crown

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/torch-to-crown/list-diseases.md

WHAT IT DOES

What list_diseases does on Torch-to-Crown

AI agents call list_diseases to retrieve information from Torch-to-Crown without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_diseases is rated Low

Even though list_diseases 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.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_diseases safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Torch-to-Crown, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_diseases, this is the rule to start with:

list_diseases Allowed

list_diseases is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_diseases": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Torch-to-Crown, apply this rule, and every list_diseases call is checked against it from then on.

FAQ

Questions about list_diseases

What does the list_diseases tool do? +

Every tracked affliction and its current phase (incubating / active / recovering / recovered / fatal). It is categorised as a Read tool in the Torch-to-Crown MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_diseases? +

Register the Torch-to-Crown MCP server in PolicyLayer and add a rule for list_diseases: 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 Torch-to-Crown. Nothing to install.

What risk level is list_diseases? +

list_diseases is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_diseases? +

Yes. Add a rate_limit block to the list_diseases 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.

How do I block list_diseases completely? +

Set action: deny in the PolicyLayer policy for list_diseases. 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.

What MCP server provides list_diseases? +

list_diseases is provided by the Torch-to-Crown MCP server (Diogenes187/Torch-to-Crown). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Torch-to-Crown, and thousands of servers like it.

This server

All 451 Torch-to-Crown tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →