Install multiple specific skills in a single call. Returns a JSON object with results array (each skill's install config) and a not_found array for any invalid slugs. Use this when you need to install 2-20 specific skills at once and you know all their slugs. Do not use this for curated collectio...
Part of the Loaditout server.
Free to start. No card required.
AI agents use install_batch 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_batch 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_batch": {
"limits": [
{
"counter": "install_batch_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_batch 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.
Install multiple specific skills in a single call. Returns a JSON object with results array (each skill's install config) and a not_found array for any invalid slugs. Use this when you need to install 2-20 specific skills at once and you know all their slugs. Do not use this for curated collections (use install_pack instead). Maximum 20 skills per call.. 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_batch: 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_batch 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_batch 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_batch. 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_batch 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.