plos-search.article.detail
Get full detail for a single open-access PLOS article by DOI, including title, journal, publication date, authors, abstract, and subject tags. Data: api.plos.org, no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/plos-search.article.detail.md
What plos-search.article.detail does on Apibase
AI agents call plos-search.article.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 |
|---|---|---|---|
doi | string | Yes | Article DOI, e.g. "10.1371/journal.pone.0004050" (returned as "doi" in plos-search.search results). |
Parameters from the server's own tool schema.
Why plos-search.article.detail is rated Low
Retrieves published article metadata without side effects or data modification.
From the tool's definition Get full detail for a single open-access PLOS article
Attacks that exploit this kind of access
The rule that runs plos-search.article.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 plos-search.article.detail, this is the rule to start with:
plos-search.article.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 plos-search.article.detail call is checked against it from then on.
Questions about plos-search.article.detail
Get full detail for a single open-access PLOS article by DOI, including title, journal, publication date, authors, abstract, and subject tags. Data: api.plos.org, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
plos-search.article.detail 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 plos-search.article.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.
plos-search.article.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 plos-search.article.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 plos-search.article.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.
plos-search.article.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