AI agents call manage_item to permanently remove resources in FishClaw MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly performs delete operations on marketplace listings, which are irreversible (deletion) or at minimum destructive (delisting removes items from sale). Automatic confirmation dialog handling bypasses user safeguards, increasing blast radius. Deletion is irreversible, placing this firmly in the Destructive category.
From the tool's definition 下架或删除操作 (take down or delete operation) — the tool performs delisting or deletion of items, including handling confirmation dialogs automatically
Documented attack patterns abuse exactly the kind of access manage_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FishClaw MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_item:
{
"version": "1",
"default": "deny",
"hide": [
"manage_item"
]
}manage_item disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
对指定商品执行下架或删除操作，内部自动跳转商品详情页并处理确认弹窗。. It is categorised as a Destructive tool in the FishClaw MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FishClaw MCP server in PolicyLayer and add a rule for manage_item: 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 FishClaw MCP. Nothing to install.
manage_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the manage_item 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 manage_item. 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.
manage_item is provided by the FishClaw MCP server (tnoobt/fishclaw_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FishClaw MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 FishClaw MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.