maker_create_learner
Create a new learner profile. Admin-only. Captures consent (parent/guardian/teacher). Stored as a research_project with type=
This record as markdown: /tools/kh0pper-crow/maker-create-learner.md
What maker_create_learner does on Crow
AI agents use maker_create_learner 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_create_learner is rated Medium
This tool creates and stores new data structures (learner profiles and research projects) with consent capture. While it has admin-only access controls and handles sensitive information (learner/guardian data), the operation is reversible (profiles can be deleted or modified). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states 'Create a new learner profile' - the verb 'create' indicates data creation. The tool captures consent information and stores data as a 'research_project', which are persistent, reversible write operations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs maker_create_learner 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_create_learner, this is the rule to start with:
maker_create_learner 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_create_learner call is checked against it from then on.
Questions about maker_create_learner
Create a new learner profile. Admin-only. Captures consent (parent/guardian/teacher). Stored as a research_project with type=. 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_create_learner: 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_create_learner 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_create_learner 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_create_learner. 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_create_learner 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