figshare.articles.details
Get full metadata for a Figshare research article by its article_id (from figshare.search): description, citation, authors with ORCID IDs, tags, subject categories, license, version, publish/modified dates, and downloadable files with direct download URLs, sizes, and MIME types. Data: Figshare.co...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/figshare.articles.details.md
What figshare.articles.details does on Apibase
AI agents call figshare.articles.details 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 |
|---|---|---|---|
article_id | integer | Yes | Figshare article ID (e.g. 33350571) — obtained from figshare.search results. |
Parameters from the server's own tool schema.
Why figshare.articles.details is rated Low
Tool retrieves publicly available research metadata without modification or execution capabilities.
From the tool's definition Get full metadata for Figshare research article by article_id, no auth required
Attacks that exploit this kind of access
The rule that runs figshare.articles.details 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.details, this is the rule to start with:
figshare.articles.details 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.details call is checked against it from then on.
Questions about figshare.articles.details
Get full metadata for a Figshare research article by its article_id (from figshare.search): description, citation, authors with ORCID IDs, tags, subject categories, license, version, publish/modified dates, and downloadable files with direct download URLs, sizes, and MIME types. 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.details accepts 1 parameter: article_id. Required: article_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 figshare.articles.details: 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.details 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.details 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.details. 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.details 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