AI agents use sync_nei_project to create or update resources in Nei — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nei environment.
This tool fetches data from a remote platform and writes/updates the local cache. It is not purely a read operation because it modifies local state (cache update). It is not destructive since it overwrites cache with newer data reversibly. The closest category is Write, as it creates/modifies local cached data.
From the tool's definition 强制从远程NEI平台同步最新的项目数据，并更新本地缓存 (force sync from remote NEI platform and update local cache)
Attacks that exploit this kind of access
强制从远程NEI平台同步最新的项目数据，并更新本地缓存。当怀疑本地数据不是最新，或需要获取最近刚刚变更的后端接口、数据模型信息时，应首先调用此工具。注意：此为强制同步操作，会触发网络请求，请仅在必要时执行一次，避免重复请求。. It is categorised as a Write tool in the Nei MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nei MCP server in PolicyLayer and add a rule for sync_nei_project: 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.
sync_nei_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sync_nei_project 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 sync_nei_project. 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.
sync_nei_project 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 →