AI agents call search_papers to retrieve information from ModelScope MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search query operation, which retrieves or queries data without side effects. This is characteristic of a Read category tool. Confidence is moderate (0.7) rather than high because the tool description is empty, leaving some ambiguity about its exact functionality, but the naming convention and context strongly suggest it is a simple search/discovery tool.
From the tool's definition Tool name 'search_papers' indicates a search operation. The parent server description mentions 'resource discovery' as a capability, and this tool appears to fit that pattern alongside other 'search_*' tools (search_datasets, search_mcp_servers,…
Documented attack patterns abuse exactly the kind of access search_papers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ModelScope MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_papers:
{
"version": "1",
"default": "deny",
"tools": {
"search_papers": {}
}
}search_papers 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. It is categorised as a Read tool in the ModelScope MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ModelScope MCP Server MCP server in PolicyLayer and add a rule for search_papers: 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 ModelScope MCP Server. Nothing to install.
search_papers 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 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. 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 is provided by the ModelScope MCP Server MCP server (modelscope/modelscope-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ModelScope 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.
9 ModelScope MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.