Resolve and ingest a full-text PDF from DOI/URL/local file, then parse into a structured document using GROBID/simple fallback pipeline.
AI agents use ingest_paper_fulltext to create or update resources in ScholarMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScholarMCP environment.
This tool fetches a PDF and writes/stores a parsed structured document into the system. It creates new data (the ingested, parsed document) in the research workflow, making it a Write operation. It is reversible in the sense that the ingested document could be removed.
From the tool's definition Resolve and ingest a full-text PDF from DOI/URL/local file, then parse into a structured document
Documented attack patterns abuse exactly the kind of access ingest_paper_fulltext gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ScholarMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for ingest_paper_fulltext:
{
"version": "1",
"default": "deny",
"tools": {
"ingest_paper_fulltext": {
"limits": [
{
"counter": "ingest_paper_fulltext_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} ingest_paper_fulltext stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Resolve and ingest a full-text PDF from DOI/URL/local file, then parse into a structured document using GROBID/simple fallback pipeline. It is categorised as a Write tool in the ScholarMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Scholar MCP server in PolicyLayer and add a rule for ingest_paper_fulltext: 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 ScholarMCP. Nothing to install.
ingest_paper_fulltext is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ingest_paper_fulltext 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 ingest_paper_fulltext. 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.
ingest_paper_fulltext is provided by the Scholar MCP server (lstudlo/scholarmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ScholarMCP, 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.
10 ScholarMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.