add_render_job

Add a render job to the queue based on current render settings.

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/add-render-job.md

WHAT IT DOES

What add_render_job does on Aos

AI agents invoke add_render_job 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 add_render_job is rated High

Triggers an external rendering operation that consumes resources and produces output files.

From the tool's definition Add a render job to the queue based on current render settings

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add_render_job 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 add_render_job, this is the rule to start with:

add_render_job Rate-limited

add_render_job 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": {
    "add_render_job": {
      "limits": [
        {
          "counter": "add_render_job_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 add_render_job call is checked against it from then on.

FAQ

Questions about add_render_job

What does the add_render_job tool do? +

Add a render job to the queue based on current render settings. 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 add_render_job? +

Register the Aos MCP server in PolicyLayer and add a rule for add_render_job: 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 add_render_job? +

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

Can I rate-limit add_render_job? +

Yes. Add a rate_limit block to the add_render_job 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 add_render_job completely? +

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

add_render_job 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

All high-risk MCP tools → The MCP Attack Database →

Guides

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