AI agents call get_pubmed_article_metadata 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 metadata about PubMed articles without modifying any data. Metadata retrieval is a query operation with no side effects. While the description is empty, the tool name and server purpose clearly indicate a read-only function. The low severity reflects that PubMed is a public resource and metadata retrieval cannot harm data integrity or systems.
From the tool's definition Tool name 'get_pubmed_article_metadata' combined with server context indicates retrieval of article metadata from PubMed.
Documented attack patterns abuse exactly the kind of access get_pubmed_article_metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PubMed-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_pubmed_article_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get_pubmed_article_metadata": {}
}
}get_pubmed_article_metadata 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.
get_pubmed_article_metadata. 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_pubmed_article_metadata: 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_pubmed_article_metadata 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_pubmed_article_metadata 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_pubmed_article_metadata. 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_pubmed_article_metadata is provided by the PubMed-MCP-Server MCP server (jackkuo666/pubmed-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PubMed-MCP-Server, 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.
4 PubMed-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.