load_project

Load/open a project by name.

SERVERAos SOURCE@hybridlabor-api/aos

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/load-project.md

WHAT IT DOES

What load_project does on Aos

AI agents invoke load_project to trigger actions in Aos. 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.

RISK

Why load_project is rated High

Opening a project triggers an external operation with side effects beyond simple data retrieval.

From the tool's definition Load/open a project by name

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs load_project safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For load_project, this is the rule to start with:

load_project Rate-limited

load_project 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "load_project": {
      "limits": [
        {
          "counter": "load_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every load_project call is checked against it from then on.

FAQ

Questions about load_project

What does the load_project tool do? +

Load/open a project by name. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on load_project? +

Register the Aos MCP server in PolicyLayer and add a rule for load_project: 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 Aos. Nothing to install.

What risk level is load_project? +

load_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit load_project? +

Yes. Add a rate_limit block to the load_project 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.

How do I block load_project completely? +

Set action: deny in the PolicyLayer policy for load_project. 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.

What MCP server provides load_project? +

load_project is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools → High-risk tools on this server →

Across the catalogue

load_script on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →