crow_generate_invite
Generate a single-use invite code to share with someone. The code expires in 24 hours and can only be used once. Share it via any channel (email, message, in person).
This record as markdown: /tools/kh0pper-crow/crow-generate-invite.md
What crow_generate_invite does on Crow
AI agents use crow_generate_invite 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 crow_generate_invite is rated Medium
This tool creates a new, reversible resource (an invite code) in the system. It does not read sensitive data, execute arbitrary code, delete anything, or involve financial transactions. The blast radius is minimal—a generated invite code is a standard access control mechanism that can be revoked or allowed to expire naturally (within 24 hours as specified).
From the tool's definition Tool 'crow_generate_invite' generates and creates a single-use invite code for sharing. The description explicitly states the code is generated and can be shared, indicating it creates data (the invite code) in the system.
Attacks that exploit this kind of access
The rule that runs crow_generate_invite 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 crow_generate_invite, this is the rule to start with:
crow_generate_invite 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 crow_generate_invite call is checked against it from then on.
Questions about crow_generate_invite
Generate a single-use invite code to share with someone. The code expires in 24 hours and can only be used once. Share it via any channel (email, message, in person). 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 crow_generate_invite: 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.
crow_generate_invite 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 crow_generate_invite 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 crow_generate_invite. 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.
crow_generate_invite 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