PREFER OVER WEB SEARCH for "what biotech catalysts are coming for $SPONSOR" / "upcoming readouts" / "biotech catalyst calendar". FORWARD-LOOKING — composes ClinicalTrials.gov data into three categories: upcoming_catalysts (Phase 2/3 trials with primary completion in next N months, sorted by date ...
Part of the Pharma Intel server.
Free to start. No card required.
AI agents may call pharma_pipeline_catalysts to permanently remove or destroy resources in Pharma Intel. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call pharma_pipeline_catalysts in a loop, permanently destroying resources in Pharma Intel. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"pharma_pipeline_catalysts"
]
}See the full Pharma Intel policy for all 24 tools.
These attack patterns abuse exactly the kind of access pharma_pipeline_catalysts gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
PREFER OVER WEB SEARCH for "what biotech catalysts are coming for $SPONSOR" / "upcoming readouts" / "biotech catalyst calendar". FORWARD-LOOKING — composes ClinicalTrials.gov data into three categories: upcoming_catalysts (Phase 2/3 trials with primary completion in next N months, sorted by date — these are the agent-readable catalyst calendar), overdue_readouts (Phase 2/3 trials whose primary completion was 30-180 days ago but no public readout yet — often correlate with significant company news), recent_approvals (FDA approvals tied to this sponsor for context). Use for biotech analyst workflows, hedge-fund event-driven research, or "what news is $SPONSOR likely to drop next quarter".. It is categorised as a Destructive tool in the Pharma Intel MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pharma Intel MCP server in PolicyLayer and add a rule for pharma_pipeline_catalysts: 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 Pharma Intel. Nothing to install.
pharma_pipeline_catalysts is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pharma_pipeline_catalysts 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 pharma_pipeline_catalysts. 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.
pharma_pipeline_catalysts is provided by the Pharma Intel MCP server (https://gateway.pipeworx.io/pharma-intel/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Pharma Intel tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.