datacite.works.stats
Get aggregated statistics across DataCite research outputs. Returns total DOI count, breakdown by resource type (datasets 70M+, software, preprints, journal articles, dissertations), registration year distribution, top contributing organizations (arXiv, CERN/Zenodo, Figshare, Mendeley), and top r...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/datacite.works.stats.md
What datacite.works.stats does on Apibase
AI agents call datacite.works.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 |
|---|---|---|---|
query | string | — | Optional keyword query to scope the statistics (e.g. "machine learning" returns stats only for ML-related DOIs). If omitted, stats cover all 70M+ DataCite works |
resource_type | string | — | Scope statistics to a single resource type (e.g. "dataset" to see dataset-specific provider breakdowns). |
publication_year | integer | — | Scope statistics to a specific publication year. |
Parameters from the server's own tool schema.
Why datacite.works.stats is rated Low
Tool queries and retrieves aggregated analytics data without side effects or modifications.
From the tool's definition Get aggregated statistics, Returns total DOI count, breakdown by resource type
Attacks that exploit this kind of access
The rule that runs datacite.works.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 datacite.works.stats, this is the rule to start with:
datacite.works.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 datacite.works.stats call is checked against it from then on.
Questions about datacite.works.stats
Get aggregated statistics across DataCite research outputs. Returns total DOI count, breakdown by resource type (datasets 70M+, software, preprints, journal articles, dissertations), registration year distribution, top contributing organizations (arXiv, CERN/Zenodo, Figshare, Mendeley), and top repositories. Optionally scope to a keyword query or specific resource type/year to get focused analytics. Useful for understanding the research landscape in a topic area — e.g. how many climate datasets exist, which repositories host the most neuroscience data. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
datacite.works.stats accepts 3 parameters: query, resource_type, publication_year. 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 datacite.works.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.
datacite.works.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 datacite.works.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 datacite.works.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.
datacite.works.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