skill_crud
A execute tool on the Skill Management MCP server.
This record as markdown: /tools/fkesheh-skill-mcp/skill-crud.md
What skill_crud does on Skill Management MCP Server
AI agents invoke skill_crud to trigger actions in Skill Management MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why skill_crud is rated High
CRUD operations on 'skills' in this context likely involve creating, reading, updating, and deleting skill definitions/scripts. The most severe applicable category across CRUD is Destructive (delete operations). However, since the description is empty and the tool name only says 'crud', there is uncertainty.
From the tool's definition Tool name 'skill_crud' on a server described as enabling Claude to 'create, edit, run, and manage reusable skills' with 'executing scripts with automatic dependency management'. Sibling tools include 'execute_python_code' and 'run_skill_script'.
Attacks that exploit this kind of access
The rule that runs skill_crud safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Skill Management MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For skill_crud, this is the rule to start with:
skill_crud stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Skill Management MCP Server, apply this rule, and every skill_crud call is checked against it from then on.
Questions about skill_crud
skill_crud is a execute tool on the Skill Management MCP Server MCP server. It is categorised as a Execute tool in the Skill Management MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Skill Management MCP Server MCP server in PolicyLayer and add a rule for skill_crud: 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 Skill Management MCP Server. Nothing to install.
skill_crud is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the skill_crud 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_crud. 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_crud is provided by the Skill Management MCP Server MCP server (fkesheh/skill-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Skill Management MCP Server, and thousands of servers like it.
Across the catalogue