material.create
Propose an evidence-bound appearance profile with no geometry authority.
This record as markdown: /tools/visionmcp/material.create.md
What material.create does on Visionmcp
AI agents use material.create to create or update resources in Visionmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Visionmcp environment.
Why material.create is rated Medium
The tool creates a new appearance/material profile. This is a Write operation — it proposes and records a new data artifact. It has no geometry authority and no indication of irreversible destruction, financial impact, or code execution. Severity is low given the scoped, non-destructive nature of creating a material profile.
From the tool's definition 'create' in tool name; 'Propose an evidence-bound appearance profile' in description
Attacks that exploit this kind of access
The rule that runs material.create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For material.create, this is the rule to start with:
material.create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Visionmcp, apply this rule, and every material.create call is checked against it from then on.
Questions about material.create
Propose an evidence-bound appearance profile with no geometry authority. It is categorised as a Write tool in the Visionmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vision MCP server in PolicyLayer and add a rule for material.create: 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 Visionmcp. Nothing to install.
material.create 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 material.create 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 material.create. 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.
material.create is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
This server
Across the catalogue