list_fda_approvals
List FDA-approved oncology drugs with indication, company, approval date, and label links. Filter by cancer type, keyword, or approval date.
This record as markdown: /tools/io-github-hifarrer-cure-cancer-with-ai/list-fda-approvals.md
What list_fda_approvals does on Cure Cancer With AI
AI agents call list_fda_approvals to retrieve information from Cure Cancer With 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 |
|---|---|---|---|
to | string | — | ISO date upper bound (e.g. 2024-12-31). |
from | string | — | ISO date lower bound (e.g. 2024-01-01). |
limit | integer | — | Results per page (1–100, default 20). |
offset | integer | — | Number of results to skip (default 0). |
search | string | — | Keyword search across drug name, generic name, and indication. |
cancerType | string | — | Filter by cancer type, e.g. lung, breast, prostate, colorectal, melanoma, leukemia, lymphoma. |
Parameters from the server's own tool schema.
Why list_fda_approvals is rated Low
This tool retrieves and filters publicly available FDA approval information without side effects. It does not create, modify, delete, or execute any operations—it only queries and returns data. The blast radius of misuse is minimal since the data is already public and read-only access poses no risk.
From the tool's definition Tool name 'list_fda_approvals' and description 'List FDA-approved oncology drugs' indicate a retrieval/query operation that returns existing public data (FDA approvals, indications, approval dates, and links).
Attacks that exploit this kind of access
The rule that runs list_fda_approvals safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cure Cancer With AI, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_fda_approvals, this is the rule to start with:
list_fda_approvals 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 Cure Cancer With AI, apply this rule, and every list_fda_approvals call is checked against it from then on.
Questions about list_fda_approvals
List FDA-approved oncology drugs with indication, company, approval date, and label links. Filter by cancer type, keyword, or approval date. It is categorised as a Read tool in the Cure Cancer With AI MCP Server, which means it retrieves data without modifying state.
list_fda_approvals accepts 6 parameters: to, from, limit, offset, search, cancerType. The full parameter table on this page comes from the server's own tool schema.
Register the Cure Cancer With AI MCP server in PolicyLayer and add a rule for list_fda_approvals: 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 Cure Cancer With AI. Nothing to install.
list_fda_approvals 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_fda_approvals 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_fda_approvals. 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_fda_approvals is provided by the Cure Cancer With AI MCP server (https://www.curecancerwithai.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cure Cancer With AI, and thousands of servers like it.
This server
Across the catalogue