datacite.doi.lookup
Get full metadata for a specific DataCite DOI. Returns the complete scholarly metadata record: title, all creators with ORCID identifiers and affiliations, publisher, publication year, resource type, abstract, subjects, license, funding references (funder name, award number), related identifiers,...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/datacite.doi.lookup.md
What datacite.doi.lookup does on Apibase
AI agents use datacite.doi.lookup to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
doi | string | Yes | The DOI to look up. Accepts bare DOI (e.g. "10.5281/zenodo.3490396") or full URL form ("https://doi.org/10.5281/zenodo.3490396"). Must be a DataCite-registered |
Parameters from the server's own tool schema.
Why datacite.doi.lookup is rated Medium
An AI agent can call datacite.doi.lookup faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs datacite.doi.lookup 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.doi.lookup, this is the rule to start with:
datacite.doi.lookup stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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.doi.lookup call is checked against it from then on.
Questions about datacite.doi.lookup
Get full metadata for a specific DataCite DOI. Returns the complete scholarly metadata record: title, all creators with ORCID identifiers and affiliations, publisher, publication year, resource type, abstract, subjects, license, funding references (funder name, award number), related identifiers, language, formats, usage metrics (views, downloads, citations), and registration/update timestamps. Accepts bare DOI (e.g. "10.5281/zenodo.3490396") or full URL form. Most Zenodo, Dryad, Figshare, and institutional repository DOIs are registered with DataCite. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
datacite.doi.lookup accepts 1 parameter: doi. Required: doi. 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.doi.lookup: 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.doi.lookup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the datacite.doi.lookup 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.doi.lookup. 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.doi.lookup 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