clinicaltrials.trials.stats
Get current statistics for the ClinicalTrials.gov database: total registered studies count and average record size in bytes. Useful for understanding data scale before bulk queries. Source: ClinicalTrials.gov v2 /stats/size endpoint (NIH US Gov, public domain, unlimited access).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/clinicaltrials.trials.stats.md
What clinicaltrials.trials.stats does on Apibase
AI agents call clinicaltrials.trials.stats to retrieve information from Apibase 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 |
|---|---|---|---|
dummy | string | — | Unused parameter — included for schema compatibility. Leave empty. Returns total study count and average record size from ClinicalTrials.gov. |
Parameters from the server's own tool schema.
Why clinicaltrials.trials.stats is rated Low
Retrieves aggregate statistics from a public database with no side effects.
From the tool's definition Get current statistics... total registered studies count and average record size
Attacks that exploit this kind of access
The rule that runs clinicaltrials.trials.stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clinicaltrials.trials.stats, this is the rule to start with:
clinicaltrials.trials.stats 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 Apibase, apply this rule, and every clinicaltrials.trials.stats call is checked against it from then on.
Questions about clinicaltrials.trials.stats
Get current statistics for the ClinicalTrials.gov database: total registered studies count and average record size in bytes. Useful for understanding data scale before bulk queries. Source: ClinicalTrials.gov v2 /stats/size endpoint (NIH US Gov, public domain, unlimited access). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
clinicaltrials.trials.stats accepts 1 parameter: dummy. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for clinicaltrials.trials.stats: 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 Apibase. Nothing to install.
clinicaltrials.trials.stats 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 clinicaltrials.trials.stats 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 clinicaltrials.trials.stats. 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.
clinicaltrials.trials.stats is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue