maker_redeem_code
INTERNAL: redeem a one-shot code for a session token. The /kiosk/r/:code HTTP handler calls this server-side. Uses UPDATE...RETURNING so a race produces exactly one winner; expired codes fail atomically.
This record as markdown: /tools/kh0pper-crow/maker-redeem-code.md
What maker_redeem_code does on Crow
AI agents use maker_redeem_code 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_redeem_code is rated Medium
This tool creates or modifies authentication state by redeeming a code for a session token. While it does not delete data, it irreversibly consumes a one-shot code and generates a new session token. This is a Write operation because it creates/modifies data (token issuance) reversibly in principle, though the one-shot nature means the code cannot be reused.
From the tool's definition 'redeem a one-shot code for a session token' and 'Uses UPDATE...RETURNING' indicate the tool modifies state (consuming a code, issuing a token) in a database transaction.
Attacks that exploit this kind of access
The rule that runs maker_redeem_code 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_redeem_code, this is the rule to start with:
maker_redeem_code 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_redeem_code call is checked against it from then on.
Questions about maker_redeem_code
INTERNAL: redeem a one-shot code for a session token. The /kiosk/r/:code HTTP handler calls this server-side. Uses UPDATE...RETURNING so a race produces exactly one winner; expired codes fail atomically. 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_redeem_code: 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_redeem_code 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_redeem_code 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_redeem_code. 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_redeem_code 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