orcid.researcher.works
Get the list of publications and other works recorded on a researcher's ORCID profile: title, work type, journal title, publication date, and DOI/other external identifiers (pub.orcid.org, public ORCID data)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/orcid.researcher.works.md
What orcid.researcher.works does on Apibase
AI agents call orcid.researcher.works 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 |
|---|---|---|---|
orcid_id | string | Yes | ORCID iD, e.g. "0000-0002-1825-0097". Obtain one from orcid.search_researcher. |
Parameters from the server's own tool schema.
Why orcid.researcher.works is rated Low
Retrieves public researcher publication metadata from ORCID; no modification, deletion, or execution of external operations.
From the tool's definition Get the list of publications and other works recorded on a researcher's ORCID profile
Attacks that exploit this kind of access
The rule that runs orcid.researcher.works 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 orcid.researcher.works, this is the rule to start with:
orcid.researcher.works 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 orcid.researcher.works call is checked against it from then on.
Questions about orcid.researcher.works
Get the list of publications and other works recorded on a researcher's ORCID profile: title, work type, journal title, publication date, and DOI/other external identifiers (pub.orcid.org, public ORCID data). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
orcid.researcher.works accepts 1 parameter: orcid_id. Required: orcid_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 orcid.researcher.works: 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.
orcid.researcher.works 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 orcid.researcher.works 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 orcid.researcher.works. 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.
orcid.researcher.works 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