Create a new learner profile. Admin-only. Captures consent (parent/guardian/teacher). Stored as a research_project with type=
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.
This tool creates and stores new learner profiles with personal and consent information. While admin-only, it is a Write operation (creates new records reversibly) rather than Execute or Destructive, as profiles can be modified or removed.
From the tool's definition Tool name 'maker_create_learner' and description 'Create a new learner profile' indicates data creation. Description mentions capturing consent data and storage in a research project, confirming reversible data modification.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access maker_create_learner 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_create_learner:
{
"version": "1",
"default": "deny",
"tools": {
"maker_create_learner": {
"limits": [
{
"counter": "maker_create_learner_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
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.
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.