nihreporter.publications.by_project
Retrieve PubMed IDs (PMIDs) of publications linked to a specific NIH core project number (e.g. "R01CA123456"). Returns up to 100 PMIDs per call with direct PubMed URLs. Use the core_project_num field from nihreporter.projects.search results. Chain with education.pubmed_search to fetch full titles...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nihreporter.publications.by-project.md
What nihreporter.publications.by_project does on Apibase
AI agents call nihreporter.publications.by_project 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 |
|---|---|---|---|
limit | integer | — | Number of publication PMIDs to return (1–100, default 50) |
offset | integer | — | Pagination offset — number of results to skip (default 0) |
core_project_num | string | Yes | NIH core project number (e.g. "R01CA123456", "U54GM115371"). Returned as core_project_num in projects.search results. |
Parameters from the server's own tool schema.
Why nihreporter.publications.by_project is rated Low
Tool queries and retrieves publication metadata with no side effects or modifications.
From the tool's definition Retrieve PubMed IDs of publications linked to specific NIH project number.
Attacks that exploit this kind of access
The rule that runs nihreporter.publications.by_project 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 nihreporter.publications.by_project, this is the rule to start with:
nihreporter.publications.by_project 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 nihreporter.publications.by_project call is checked against it from then on.
Questions about nihreporter.publications.by_project
Retrieve PubMed IDs (PMIDs) of publications linked to a specific NIH core project number (e.g. "R01CA123456"). Returns up to 100 PMIDs per call with direct PubMed URLs. Use the core_project_num field from nihreporter.projects.search results. Chain with education.pubmed_search to fetch full titles and abstracts. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nihreporter.publications.by_project accepts 3 parameters: limit, offset, core_project_num. Required: core_project_num. 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 nihreporter.publications.by_project: 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.
nihreporter.publications.by_project 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 nihreporter.publications.by_project 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 nihreporter.publications.by_project. 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.
nihreporter.publications.by_project 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