doaj.articles.detail
Retrieve full metadata for a single open access article from the Directory of Open Access Journals by its DOAJ article ID. Returns complete bibliographic record including all authors, journal title, ISSN, publication year and month, subject classifications, full keyword list, full abstract, DOI, ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/doaj.articles.detail.md
What doaj.articles.detail does on Apibase
AI agents call doaj.articles.detail 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 | string | Yes | DOAJ article identifier (32-character hex string, e.g. "000004687a3a411cb466625281f2ceb0"). Obtain from article_search results. |
Parameters from the server's own tool schema.
Why doaj.articles.detail is rated Low
Tool retrieves bibliographic article metadata with no side effects, modifications, or external action execution.
From the tool's definition Retrieve full metadata for a single open access article by its DOAJ article ID.
Attacks that exploit this kind of access
The rule that runs doaj.articles.detail 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 doaj.articles.detail, this is the rule to start with:
doaj.articles.detail 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 doaj.articles.detail call is checked against it from then on.
Questions about doaj.articles.detail
Retrieve full metadata for a single open access article from the Directory of Open Access Journals by its DOAJ article ID. Returns complete bibliographic record including all authors, journal title, ISSN, publication year and month, subject classifications, full keyword list, full abstract, DOI, and direct full-text URL. Use after doaj.articles.search to get complete details for a specific article. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
doaj.articles.detail 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 doaj.articles.detail: 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.
doaj.articles.detail 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 doaj.articles.detail 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 doaj.articles.detail. 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.
doaj.articles.detail 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