AI agents use update_recommendations to create or update resources in Juejin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Juejin environment.
This tool creates or modifies user preference data reversibly (recommendations can be updated again). It does not delete data irreversibly, execute external code, move money, or perform destructive operations. The modification is scoped to recommendation settings and user interest associations, making it a Write-category tool.
From the tool's definition Tool name 'update_recommendations' combined with description indicating it modifies user recommendations based on behavior and interests. The verb '更新' (update) in Chinese explicitly indicates modification of data.
Attacks that exploit this kind of access
更新用户推荐,基于最新的用户行为和兴趣. It is categorised as a Write tool in the Juejin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Juejin MCP server in PolicyLayer and add a rule for update_recommendations: 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 Juejin. Nothing to install.
update_recommendations 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 update_recommendations 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 update_recommendations. 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.
update_recommendations is provided by the Juejin MCP server (ztxtxwd/juejin-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 →