AI agents use like_article 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 writes a 'like' interaction to an article on Juejin. It requires authorization ('需要授权'), indicating it performs an authenticated state-changing operation. Since likes are generally reversible (can be unliked), this falls under Write rather than Destructive. Misuse could involve mass-liking content to manipulate engagement metrics, giving it a medium severity.
From the tool's definition 点赞文章 (like article) — creates a 'like' interaction on an article, which is a reversible write action (likes can typically be undone)
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 like_article: 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.
like_article 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 like_article 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 like_article. 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.
like_article 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 →