maker_set_mode
Switch deployment mode between solo, family, classroom. Admin-only. Downgrading family→solo refuses if more than one learner profile exists (use the Archive & Downgrade flow in the panel instead).
This record as markdown: /tools/kh0pper-crow/maker-set-mode.md
What maker_set_mode does on Crow
AI agents use maker_set_mode 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_set_mode is rated Medium
This tool creates or modifies system-level configuration (deployment mode switching) with reversible effects. While admin-only, an authorized AI agent misusing this could disrupt multi-user deployments by downgrading modes inappropriately or changing sharing/collaboration scope across the Crow platform. The refusal logic mitigates but doesn't eliminate risk.
From the tool's definition Tool description: 'Switch deployment mode between solo, family, classroom' with explicit admin-only restriction and data-dependent logic ('Downgrading family→solo refuses if more than one learner profile exists').
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs maker_set_mode 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_set_mode, this is the rule to start with:
maker_set_mode 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_set_mode call is checked against it from then on.
Questions about maker_set_mode
Switch deployment mode between solo, family, classroom. Admin-only. Downgrading family→solo refuses if more than one learner profile exists (use the Archive & Downgrade flow in the panel instead). 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_set_mode: 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_set_mode 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_set_mode 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_set_mode. 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_set_mode 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