Enrich a dataset or paper by DOI: resolve open-access links, PDF URLs, citation counts, and reference graphs via Unpaywall, OpenCitations, and NIH iCite
AI agents call enrich_result to retrieve information from MobusMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The enrich_result tool performs read-only operations: looking up bibliographic metadata (DOI resolution, citation counts, reference graphs) from external academic databases (Unpaywall, OpenCitations, NIH iCite) and returning enriched data. It has no side effects on the original dataset or paper, cannot execute code, delete data, or create financial obligations.
From the tool's definition Tool description states it 'resolves open-access links, PDF URLs, citation counts, and reference graphs' — purely retrieval and querying operations with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access enrich_result gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MobusMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for enrich_result:
{
"version": "1",
"default": "deny",
"tools": {
"enrich_result": {}
}
} enrich_result is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Enrich a dataset or paper by DOI: resolve open-access links, PDF URLs, citation counts, and reference graphs via Unpaywall, OpenCitations, and NIH iCite. It is categorised as a Read tool in the MobusMCP MCP Server, which means it retrieves data without modifying state.
Register the Mobus MCP server in PolicyLayer and add a rule for enrich_result: 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 MobusMCP. Nothing to install.
enrich_result 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 enrich_result 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 enrich_result. 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.
enrich_result is provided by the Mobus MCP server (mobus-ai/mobus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MobusMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 MobusMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.