Write the OpenSCAD source file for a 3D component and trigger the render pipeline. If uuid is omitted, a new UUID is generated automatically. Creates metadata.json with the component name. Returns the UUID. Use get_job_result(uuid) to poll the pipeline.
Risk signalsAccepts raw HTML/template content (content)
Part of the Tesseract server.
Free to start. No card required.
AI agents use studio_write_scad to create or modify resources in Tesseract. 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 studio_write_scad 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 Tesseract.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"studio_write_scad": {
"limits": [
{
"counter": "studio_write_scad_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Tesseract policy for all 46 tools.
These attack patterns abuse exactly the kind of access studio_write_scad 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.
Write the OpenSCAD source file for a 3D component and trigger the render pipeline. If uuid is omitted, a new UUID is generated automatically. Creates metadata.json with the component name. Returns the UUID. Use get_job_result(uuid) to poll the pipeline.. It is categorised as a Write tool in the Tesseract MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tesseract MCP server in PolicyLayer and add a rule for studio_write_scad: 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 Tesseract. Nothing to install.
studio_write_scad 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 studio_write_scad 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 studio_write_scad. 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.
studio_write_scad is provided by the Tesseract MCP server (tesseract-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 46 Tesseract 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.