crow_accept_short_invite
Accept a short pairing code someone read aloud or typed to you. Looks up the pairing rendezvous on the relay network and completes the connection. Shows a safety number for out-of-band verification.
This record as markdown: /tools/kh0pper-crow/crow-accept-short-invite.md
What crow_accept_short_invite does on Crow
AI agents use crow_accept_short_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_accept_short_invite is rated Medium
The tool accepts and finalizes a pairing connection based on a short code, which modifies the system state by establishing a new encrypted P2P relationship. This is a Write operation—it creates a new data relationship (pairing) that is reversible (can be unpairing later).
From the tool's definition Accept a short pairing code...completes the connection. This creates or modifies a connection/pairing relationship in the system, establishing a new secure link between participants.
Attacks that exploit this kind of access
The rule that runs crow_accept_short_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_accept_short_invite, this is the rule to start with:
crow_accept_short_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_accept_short_invite call is checked against it from then on.
Questions about crow_accept_short_invite
Accept a short pairing code someone read aloud or typed to you. Looks up the pairing rendezvous on the relay network and completes the connection. Shows a safety number for out-of-band verification. 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_accept_short_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_accept_short_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_accept_short_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_accept_short_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_accept_short_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