check_generation
Collect a 3D generation that was still rendering when generate_3d_model returned. Pass the job_id from that result. While it is still working you get updated timing; when it is done you get the model.
This record as markdown: /tools/3d-ar-studio-mcp/check-generation.md
What check_generation does on 3d Ar Studio
AI agents call check_generation to retrieve information from 3d Ar Studio without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | Yes | The job_id from a pending generation. |
Parameters from the server's own tool schema.
Why check_generation is rated Low
Even though check_generation only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs check_generation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 3d Ar Studio, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_generation, this is the rule to start with:
check_generation is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 3d Ar Studio, apply this rule, and every check_generation call is checked against it from then on.
Questions about check_generation
Collect a 3D generation that was still rendering when generate_3d_model returned. Pass the job_id from that result. While it is still working you get updated timing; when it is done you get the model. It is categorised as a Read tool in the 3d Ar Studio MCP Server, which means it retrieves data without modifying state.
check_generation accepts 1 parameter: job_id. Required: job_id. The full parameter table on this page comes from the server's own tool schema.
Register the 3d Ar Studio MCP server in PolicyLayer and add a rule for check_generation: 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 3d Ar Studio. Nothing to install.
check_generation 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 check_generation 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 check_generation. 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.
check_generation is provided by the 3d Ar Studio MCP server (3d-ar-studio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 3d Ar Studio, and thousands of servers like it.
This server
Across the catalogue