doaj.journals.detail
Retrieve full metadata for a single open access journal from the Directory of Open Access Journals by its DOAJ journal ID. Returns comprehensive bibliographic and quality metadata including aims & scope URL, author instructions, peer-review process type, BOAI compliance status, APC pricing in EUR...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/doaj.journals.detail.md
What doaj.journals.detail does on Apibase
AI agents call doaj.journals.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 |
|---|---|---|---|
journal_id | string | Yes | DOAJ journal identifier (32-character hex string, e.g. "4b3d6d1e61534f8d84b64b5c5a9a4cd0"). Obtain from journal_search results. |
Parameters from the server's own tool schema.
Why doaj.journals.detail is rated Low
Tool retrieves journal metadata from a public directory with no side effects or data modification capabilities.
From the tool's definition Retrieve full metadata for a single open access journal, Returns comprehensive bibliographic and quality metadata
Attacks that exploit this kind of access
The rule that runs doaj.journals.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.journals.detail, this is the rule to start with:
doaj.journals.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.journals.detail call is checked against it from then on.
Questions about doaj.journals.detail
Retrieve full metadata for a single open access journal from the Directory of Open Access Journals by its DOAJ journal ID. Returns comprehensive bibliographic and quality metadata including aims & scope URL, author instructions, peer-review process type, BOAI compliance status, APC pricing in EUR, preservation archiving services, and all ISSN variants. Use after doaj.journals.search to get complete details for a specific journal. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
doaj.journals.detail accepts 1 parameter: journal_id. Required: journal_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.journals.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.journals.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.journals.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.journals.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.journals.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