get_literature_article_by_pmid
AI agents call get_literature_article_by_pmid to retrieve information from Literature MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves published literature records from the Europe PMC database using a PubMed identifier. This is a retrieval operation with no side effects—it queries and returns existing data without modifying, executing code, deleting, or moving funds.
From the tool's definition Tool name 'get_literature_article_by_pmid' indicates retrieval of literature articles by PubMed identifier (PMID). Context indicates the server provides 'retrieval' and 'gather...published research' operations.
Attacks that exploit this kind of access
get_literature_article_by_pmid. It is categorised as a Read tool in the Literature MCP MCP Server, which means it retrieves data without modifying state.
Register the Literature MCP server in PolicyLayer and add a rule for get_literature_article_by_pmid: 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 Literature MCP. Nothing to install.
get_literature_article_by_pmid 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 get_literature_article_by_pmid 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 get_literature_article_by_pmid. 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.
get_literature_article_by_pmid is provided by the Literature MCP server (saurabhsing21/literature-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →