Get full text content of PubMed articles using PMIDs.
AI agents call get_fulltext to retrieve information from PubMed MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns full text content from PubMed articles—a read-only operation with no side effects. It queries existing data without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal; an agent could retrieve sensitive or copyrighted content inappropriately, but this is a data access issue rather than a system-altering risk.
From the tool's definition Tool name 'get_fulltext' and description 'Get full text content of PubMed articles using PMIDs' indicates retrieval of published scientific article content with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get full text content of PubMed articles using PMIDs. It is categorised as a Read tool in the PubMed MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PubMed MCP Server MCP server in PolicyLayer and add a rule for get_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 PubMed MCP Server. Nothing to install.
get_fulltext 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_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 get_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.
get_fulltext is provided by the PubMed MCP Server MCP server (ncukondo/pubmed-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 →