maker_save_artifact
Save a learner-produced artifact (e.g. Blockly workspace XML, drawing). Guest sessions return a friendly
This record as markdown: /tools/kh0pper-crow/maker-save-artifact.md
What maker_save_artifact does on Crow
AI agents use maker_save_artifact to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why maker_save_artifact is rated Medium
This tool creates or stores user-generated artifacts (Blockly workspaces, drawings, etc.) which are reversible modifications. It does not delete data irreversibly (Destructive), execute arbitrary code (Execute), move funds (Financial), or merely read data (Read).
From the tool's definition Tool name contains 'save' and description states 'Save a learner-produced artifact' indicating persistent creation/modification of data.
Attacks that exploit this kind of access
The rule that runs maker_save_artifact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For maker_save_artifact, this is the rule to start with:
maker_save_artifact 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 Crow, apply this rule, and every maker_save_artifact call is checked against it from then on.
Questions about maker_save_artifact
Save a learner-produced artifact (e.g. Blockly workspace XML, drawing). Guest sessions return a friendly. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for maker_save_artifact: 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 Crow. Nothing to install.
maker_save_artifact 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 maker_save_artifact 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 maker_save_artifact. 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.
maker_save_artifact is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue