Delete a skill by name. Args: skill_name: Name of the skill to delete Returns: Success or error message
AI agents call skill_delete to permanently remove resources in Browser-Use MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a skill by name with no indicated undo mechanism. Deletion operations that cannot be reversed fall under the Destructive category. The severity is high because an agent could delete critical skills needed for browser automation workflows, disrupting dependent tasks and potentially corrupting the system state. High confidence due to explicit 'delete' terminology and irreversible nature.
From the tool's definition Tool name is 'skill_delete' with description 'Delete a skill by name.' The function performs irreversible deletion of a skill resource.
Documented attack patterns abuse exactly the kind of access skill_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browser-Use MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for skill_delete:
{
"version": "1",
"default": "deny",
"hide": [
"skill_delete"
]
}skill_delete 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.
Delete a skill by name. Args: skill_name: Name of the skill to delete Returns: Success or error message. It is categorised as a Destructive tool in the Browser-Use MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Browser-Use MCP Server MCP server in PolicyLayer and add a rule for skill_delete: 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 Browser-Use MCP Server. Nothing to install.
skill_delete 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_delete 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_delete. 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_delete is provided by the Browser-Use MCP Server MCP server (saik0s/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Browser-Use MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Browser-Use MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.