AI agents call get_pin_recommendations to retrieve information from Juejin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves personalized recommendations from Juejin without creating, modifying, deleting, or executing any operations. It is purely a data retrieval function similar to a search or query operation. The context of sibling tools (analyze_*, check_*, follow_user, collect_article) confirms this server supports read operations for content discovery.
From the tool's definition Tool name 'get_pin_recommendations' and description '获取个性化沸点推荐，基于用户兴趣和内容质量' (get personalized pin recommendations based on user interests and content quality) indicate retrieval of recommendation data with no modification or side effects.
Attacks that exploit this kind of access
获取个性化沸点推荐，基于用户兴趣和内容质量. It is categorised as a Read tool in the Juejin MCP Server, which means it retrieves data without modifying state.
Register the Juejin MCP server in PolicyLayer and add a rule for get_pin_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.
get_pin_recommendations 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 get_pin_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 get_pin_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.
get_pin_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 →