AI agents call batch_export_from_search to retrieve information from PubTator-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the server context (PubTator3 literature annotation) and the tool name suggesting a batch export operation from search results, this is most likely a read/export operation that retrieves publication data. The sibling tools (export_publications, find_entity_id, find_related_entities, search_pubtator) are all read-oriented, supporting this classification. Confidence is lowered due to empty description.
From the tool's definition Tool name 'batch_export_from_search' on a biomedical literature annotation server; description is empty and uninformative.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_export_from_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PubTator-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_export_from_search:
{
"version": "1",
"default": "deny",
"tools": {
"batch_export_from_search": {}
}
}batch_export_from_search 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.
batch_export_from_search. It is categorised as a Read tool in the PubTator-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the PubTator-MCP-Server MCP server in PolicyLayer and add a rule for batch_export_from_search: 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 PubTator-MCP-Server. Nothing to install.
batch_export_from_search 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 batch_export_from_search 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 batch_export_from_search. 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.
batch_export_from_search is provided by the PubTator-MCP-Server MCP server (jackkuo666/pubtator-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PubTator-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.
5 PubTator-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.