Save a learner-produced artifact (e.g. Blockly workspace XML, drawing). Guest sessions return a friendly
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.
The tool saves user-generated content (artifacts like Blockly workspaces or drawings) to persistent storage. This is a Write operation because it creates or modifies data without irreversible deletion. Severity is medium because unauthorized artifact saving could pollute a project with unwanted or malicious content, but the action is reversible (artifacts can be deleted or overwritten).
From the tool's definition Tool name 'maker_save_artifact' and description 'Save a learner-produced artifact' indicate the tool creates or modifies data (workspace XML, drawings) in a reversible manner.
Documented attack patterns abuse exactly the kind of access maker_save_artifact gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for maker_save_artifact:
{
"version": "1",
"default": "deny",
"tools": {
"maker_save_artifact": {
"limits": [
{
"counter": "maker_save_artifact_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.