maker_start_guest_session
Mint an ephemeral guest session (no learner profile, no memories, no transcripts, no artifact save). 30-min cap. Returns a direct short URL + preview cookie (no redemption code needed — no handoff).
This record as markdown: /tools/kh0pper-crow/maker-start-guest-session.md
What maker_start_guest_session does on Crow
AI agents invoke maker_start_guest_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.
Why maker_start_guest_session is rated High
This tool creates and starts an ephemeral session, generating a URL and cookie. It executes an operation with external side effects (minting a session token, issuing a cookie) rather than simply reading data or writing a persistent record. While the session is temporary (30-min cap, no saved data), the act of minting a session and issuing credentials is an Execute-class action.
From the tool's definition Mint an ephemeral guest session... Returns a direct short URL + preview cookie
Attacks that exploit this kind of access
The rule that runs maker_start_guest_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_guest_session, this is the rule to start with:
maker_start_guest_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every maker_start_guest_session call is checked against it from then on.
Questions about maker_start_guest_session
Mint an ephemeral guest session (no learner profile, no memories, no transcripts, no artifact save). 30-min cap. Returns a direct short URL + preview cookie (no redemption code needed — no handoff). 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.
Register the Crow MCP server in PolicyLayer and add a rule for maker_start_guest_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.
maker_start_guest_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the maker_start_guest_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.
Set action: deny in the PolicyLayer policy for maker_start_guest_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.
maker_start_guest_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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue