Request explicit permission from the human owner before installing a skill. Returns a JSON object with request_id (number) and status ('pending'). Use this for skills with security grade C or F, high risk_level, or when the skill requires sensitive permissions (filesystem, network, credentials). ...
Part of the Loaditout server.
Free to start. No card required.
AI agents call request_permission to retrieve information from Loaditout without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though request_permission only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"request_permission": {}
}
}See the full Loaditout policy for all 21 tools.
These attack patterns abuse exactly the kind of access request_permission gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Request explicit permission from the human owner before installing a skill. Returns a JSON object with request_id (number) and status ('pending'). Use this for skills with security grade C or F, high risk_level, or when the skill requires sensitive permissions (filesystem, network, credentials). Check the request status later with check_permission. Do not use this for A-graded skills unless the user has requested manual approval for all installs.. It is categorised as a Read tool in the Loaditout MCP Server, which means it retrieves data without modifying state.
Register the Loaditout MCP server in PolicyLayer and add a rule for request_permission: 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.
request_permission is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the request_permission 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 request_permission. 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.
request_permission 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.