Get the platform-specific configuration JSON needed to install a single skill. Returns a JSON object with config_path (where to write the config), config (the JSON to write), and instructions (human-readable setup steps). This tool is read-only and does NOT write any files. Use this when the user...
Part of the Loaditout server.
Free to start. No card required.
AI agents use install_skill to create or modify resources in Loaditout. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call install_skill repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Loaditout.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"install_skill": {
"limits": [
{
"counter": "install_skill_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Loaditout policy for all 21 tools.
These attack patterns abuse exactly the kind of access install_skill gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Get the platform-specific configuration JSON needed to install a single skill. Returns a JSON object with config_path (where to write the config), config (the JSON to write), and instructions (human-readable setup steps). This tool is read-only and does NOT write any files. Use this when the user wants to install a specific skill and you need the exact config for their agent platform. Do not use this for batch installs (use install_batch instead) or for packs (use install_pack instead). The skill slug is automatically saved to agent memory after calling this tool.. It is categorised as a Write tool in the Loaditout MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Loaditout MCP server in PolicyLayer and add a rule for install_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 Loaditout. Nothing to install.
install_skill is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the install_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 install_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.
install_skill is provided by the Loaditout MCP server (loaditout-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Loaditout tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.