AI agents call get_biorxiv_metadata to retrieve information from bioRxiv-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 bioRxiv papers with no described side effects, modifications, or external operations. It is a straightforward data retrieval function. The empty tool description reduces confidence slightly, but the tool name and server context clearly indicate a read operation. Severity is low because metadata access on a public preprint repository poses minimal risk.
From the tool's definition Tool name 'get_biorxiv_metadata' indicates retrieval of metadata from bioRxiv preprints. The server description states it 'allows AI models to search for biology preprints and access their' metadata, confirming read-only access to preprint information.
Documented attack patterns abuse exactly the kind of access get_biorxiv_metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and bioRxiv-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_biorxiv_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get_biorxiv_metadata": {}
}
}get_biorxiv_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_biorxiv_metadata. It is categorised as a Read tool in the bioRxiv-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the bioRxiv-MCP-Server MCP server in PolicyLayer and add a rule for get_biorxiv_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 bioRxiv-MCP-Server. Nothing to install.
get_biorxiv_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_biorxiv_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_biorxiv_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_biorxiv_metadata is provided by the bioRxiv-MCP-Server MCP server (jackkuo666/biorxiv-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from bioRxiv-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.
3 bioRxiv-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.