Remove a skill and keep a rollback backup.
AI agents call remove_skill to permanently remove resources in Friday MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs irreversible deletion of skills from the workspace. Although a backup is created for recovery purposes, the act of removal is destructive and non-atomic—the agent loses the skill's functionality immediately. This qualifies as Destructive (most severe) rather than Write, since it removes rather than modifies data, and the effects cannot be trivially reversed through normal tool operations.
From the tool's definition Tool name 'remove_skill' indicates deletion. Description states 'Remove a skill' — this is an irreversible deletion operation.
Attacks that exploit this kind of access
Remove a skill and keep a rollback backup. It is categorised as a Destructive tool in the Friday MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Friday MCP Server MCP server in PolicyLayer and add a rule for remove_skill: 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 Friday MCP Server. Nothing to install.
remove_skill 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 remove_skill 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 remove_skill. 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.
remove_skill is provided by the Friday MCP Server MCP server (jeremylakeyjr/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 →