AI agents call get_feed_detail to retrieve information from Xhs Kit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention and context from sibling tools, 'get_feed_detail' almost certainly retrieves feed content details without modifying data. No write, execute, destructive, or financial operations are implied. The empty description prevents higher confidence, but the 'get_' prefix and server context (social media automation) strongly suggest read-only behavior.
From the tool's definition Tool name 'get_feed_detail' indicates data retrieval. Sibling tools include 'list_feeds', 'get_user_profile', and query operations ('favorite_feed', 'like_feed'), establishing a pattern where 'get_*' operations are read-only.
Attacks that exploit this kind of access
get_feed_detail. It is categorised as a Read tool in the Xhs Kit MCP Server, which means it retrieves data without modifying state.
Register the Xhs Kit MCP server in PolicyLayer and add a rule for get_feed_detail: 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 Xhs Kit. Nothing to install.
get_feed_detail 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_feed_detail 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_feed_detail. 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_feed_detail is provided by the Xhs Kit MCP server (luweizheng/xhs-kit). 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 →