Reject an image for 3D model generation.
AI agents use reject_image to create or update resources in OpenSCAD MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenSCAD MCP Server environment.
This tool modifies data reversibly (images can potentially be re-submitted or restored), affecting workflow state rather than retrieving data (Read), executing arbitrary operations (Execute), or permanently destroying records (Destructive). The context of a 3D model generation pipeline suggests rejection changes image status/metadata.
From the tool's definition Tool name 'reject_image' and description 'Reject an image for 3D model generation' indicate state modification of image records in a workflow system.
Attacks that exploit this kind of access
Reject an image for 3D model generation. It is categorised as a Write tool in the OpenSCAD MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenSCAD MCP Server MCP server in PolicyLayer and add a rule for reject_image: 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 OpenSCAD MCP Server. Nothing to install.
reject_image 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 reject_image 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 reject_image. 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.
reject_image is provided by the OpenSCAD MCP Server MCP server (jhacksman/openscad-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →