AI agents call search_interfaces_by_url to retrieve information from Nei 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 interface information from NEI based on URL parameters. It is a read-only lookup operation that returns data without modifying, executing code, or causing destructive actions. The low severity reflects minimal blast radius—an AI agent misusing this tool could only retrieve interface metadata, not cause harm to systems or data.
From the tool's definition Tool description states it 'searches interface information through NEI interface detail links' and 'returns interface details precisely' by parsing pid and id from URLs.
Attacks that exploit this kind of access
通过NEI接口详情链接搜索接口信息。适用于用户直接提供形如 http://nei.example.com/interface/detail/?pid=10135&id=13015 的链接；工具只解析链接中的pid和id并精确返回接口详情，不进行URI模糊搜索。如果链接缺少pid/id或pid/id不是正整数，将返回空结果。如果搜索结果为空，建议先调用. It is categorised as a Read tool in the Nei MCP Server, which means it retrieves data without modifying state.
Register the Nei MCP server in PolicyLayer and add a rule for search_interfaces_by_url: 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 Nei. Nothing to install.
search_interfaces_by_url 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_interfaces_by_url 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_interfaces_by_url. 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_interfaces_by_url is provided by the Nei MCP server (@leila329/nei-mcp-server). 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 →