zenodo.records.files
List all downloadable files for a Zenodo record. Returns filename, MIME type, size in bytes, checksum (MD5), and a direct download URL for each file. Zenodo records can contain multiple files (data CSVs, code archives, supplementary PDFs, images, etc.). Use zenodo.records.search or zenodo.records...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/zenodo.records.files.md
What zenodo.records.files does on Apibase
AI agents call zenodo.records.files 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 |
|---|---|---|---|
limit | integer | — | Maximum number of files to return (default 50, max 100). |
record_id | string | number | Yes | Zenodo record ID whose files to list (numeric, e.g. 10487285). Obtain from zenodo.records.search or zenodo.records.detail. |
Parameters from the server's own tool schema.
Why zenodo.records.files is rated Low
Retrieves file metadata and download links from public Zenodo records without side effects.
From the tool's definition List all downloadable files, Returns filename, MIME type, size, checksum, download URL
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs zenodo.records.files 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 zenodo.records.files, this is the rule to start with:
zenodo.records.files 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 zenodo.records.files call is checked against it from then on.
Questions about zenodo.records.files
List all downloadable files for a Zenodo record. Returns filename, MIME type, size in bytes, checksum (MD5), and a direct download URL for each file. Zenodo records can contain multiple files (data CSVs, code archives, supplementary PDFs, images, etc.). Use zenodo.records.search or zenodo.records.detail to find the record ID, then call this tool to get the file manifest with direct download links. All files in open-access records are freely downloadable without authentication. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
zenodo.records.files accepts 2 parameters: limit, record_id. Required: record_id. 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 zenodo.records.files: 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.
zenodo.records.files 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 zenodo.records.files 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 zenodo.records.files. 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.
zenodo.records.files 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