Search papers published in a specific venue/journal
AI agents call search_papers_by_venue to retrieve information from AMiner 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 queries academic paper metadata filtered by publication venue. It performs a passive information retrieval operation without creating, modifying, deleting, or executing any code. The blast radius of misuse is minimal—an agent could only retrieve publicly available academic paper information, which carries no security or operational risk.
From the tool's definition Tool name is 'search_papers_by_venue' and description states 'Search papers published in a specific venue/journal'. The verb 'search' indicates a read-only query operation with no side effects.
Documented attack patterns abuse exactly the kind of access search_papers_by_venue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AMiner MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_papers_by_venue:
{
"version": "1",
"default": "deny",
"tools": {
"search_papers_by_venue": {}
}
}search_papers_by_venue 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.
Search papers published in a specific venue/journal. It is categorised as a Read tool in the AMiner MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AMiner MCP Server MCP server in PolicyLayer and add a rule for search_papers_by_venue: 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 AMiner MCP Server. Nothing to install.
search_papers_by_venue 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 search_papers_by_venue 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 search_papers_by_venue. 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.
search_papers_by_venue is provided by the AMiner MCP Server MCP server (scipenai/aminer-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AMiner 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 AMiner MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.