AI agents call skill_trash_user_asset to permanently remove resources in ClaudeSkills MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The word 'trash' in the tool name indicates a destructive operation — moving or deleting a user asset, which may be irreversible. The description is empty, reducing confidence, but the naming convention is consistent with deletion/trashing semantics. Given sibling tools like skill_add_asset and skill_read_asset, this tool likely performs the inverse (removal/deletion) of asset management operations.
From the tool's definition Tool name 'skill_trash_user_asset' contains 'trash' which strongly implies moving an asset to trash (potentially irreversible deletion) and 'user_asset' suggests it operates on user-owned assets.
Documented attack patterns abuse exactly the kind of access skill_trash_user_asset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ClaudeSkills MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for skill_trash_user_asset:
{
"version": "1",
"default": "deny",
"hide": [
"skill_trash_user_asset"
]
}skill_trash_user_asset 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.
skill_trash_user_asset. It is categorised as a Destructive tool in the ClaudeSkills MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ClaudeSkills MCP Server MCP server in PolicyLayer and add a rule for skill_trash_user_asset: 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 ClaudeSkills MCP Server. Nothing to install.
skill_trash_user_asset 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 skill_trash_user_asset 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 skill_trash_user_asset. 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.
skill_trash_user_asset is provided by the ClaudeSkills MCP Server MCP server (tsoernes/skills-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ClaudeSkills MCP Server, 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.
13 ClaudeSkills MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.