maker_start_session

Mint a new kiosk session for a learner and return a redemption code (NOT the raw token). The QR/URL carries the code; the token is issued as an HttpOnly cookie on redemption. Admin-only.

SERVERCrow SOURCEkh0pper/crow

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/maker-start-session.md

WHAT IT DOES

What maker_start_session does on Crow

AI agents invoke maker_start_session to trigger actions in Crow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why maker_start_session is rated High

This tool mints (creates and activates) a new session token and issues credentials. It is more than a simple Write because it triggers an authentication/authorization side-effect (issuing a session token as an HttpOnly cookie upon redemption), constituting an external operation with security implications. Misuse could allow unauthorized access to learner sessions, hence high severity.

From the tool's definition 'Mint a new kiosk session for a learner and return a redemption code' — creates and activates a new authenticated session; 'Admin-only' indicates privileged operation

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs maker_start_session 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_start_session, this is the rule to start with:

maker_start_session Rate-limited

maker_start_session stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "maker_start_session": {
      "limits": [
        {
          "counter": "maker_start_session_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every maker_start_session call is checked against it from then on.

FAQ

Questions about maker_start_session

What does the maker_start_session tool do? +

Mint a new kiosk session for a learner and return a redemption code (NOT the raw token). The QR/URL carries the code; the token is issued as an HttpOnly cookie on redemption. Admin-only. It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on maker_start_session? +

Register the Crow MCP server in PolicyLayer and add a rule for maker_start_session: 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.

What risk level is maker_start_session? +

maker_start_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit maker_start_session? +

Yes. Add a rate_limit block to the maker_start_session 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.

How do I block maker_start_session completely? +

Set action: deny in the PolicyLayer policy for maker_start_session. 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.

What MCP server provides maker_start_session? +

maker_start_session 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.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →