AI agents call paper_search to retrieve information from Navmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'paper_search' strongly implies a read-only academic search operation, consistent with the server description mentioning 'academic search via Selenium and FastMCP'. No destructive or write operations are implied. Confidence is lowered due to the empty description.
From the tool's definition Tool name 'paper_search' suggests a search/query operation; description is empty and uninformative.
Attacks that exploit this kind of access
paper_search. It is categorised as a Read tool in the Navmcp MCP Server, which means it retrieves data without modifying state.
Register the Nav MCP server in PolicyLayer and add a rule for paper_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 Navmcp. Nothing to install.
paper_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 paper_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 paper_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.
paper_search is provided by the Nav MCP server (jianlins/navmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →