figshare.articles.search
Search Figshare's open research repository for datasets, figures, papers, preprints, media, and other research outputs, e.g. "soil moisture" or "gene expression". Filter by free-text query, exact DOI, or research output type (dataset, figure, journal_contribution, preprint, thesis, software, etc....
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/figshare.articles.search.md
What figshare.articles.search does on Apibase
AI agents call figshare.articles.search 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 |
|---|---|---|---|
doi | string | — | Filter by exact DOI (e.g. "10.6084/m9.figshare.33350571.v1"). |
page | integer | — | Page number for pagination (default 1). |
query | string | — | Free-text search across title, description, and author (e.g. "soil moisture", "gene expression"). |
item_type | string | — | Filter by research output type: figure, media, dataset, poster, journal_contribution, presentation, thesis, software, online_resource, preprint, book, or confer |
page_size | integer | — | Results per page (default 10, max 50). |
order_direction | string | — | Sort direction by published date (default "desc" — newest first). |
Parameters from the server's own tool schema.
Why figshare.articles.search is rated Low
Tool queries public CC-licensed research data without modification or execution capabilities.
From the tool's definition Search Figshare's open research repository for datasets, figures, papers
Attacks that exploit this kind of access
The rule that runs figshare.articles.search 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 figshare.articles.search, this is the rule to start with:
figshare.articles.search 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 figshare.articles.search call is checked against it from then on.
Questions about figshare.articles.search
Search Figshare's open research repository for datasets, figures, papers, preprints, media, and other research outputs, e.g. "soil moisture" or "gene expression". Filter by free-text query, exact DOI, or research output type (dataset, figure, journal_contribution, preprint, thesis, software, etc.), sorted by publication date. Returns each article's id (for use with figshare.article_details), title, DOI, item type, publish date, and URL. Data: Figshare.com, CC-licensed research outputs, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
figshare.articles.search accepts 6 parameters: doi, page, query, item_type, page_size, order_direction. 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 figshare.articles.search: 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.
figshare.articles.search 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 figshare.articles.search 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 figshare.articles.search. 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.
figshare.articles.search 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