flocks_createJoinToken
Create an org-scoped single-use join token (admin required) (POST /v1/flocks/byom/tokens) [service status: not_deployed]
This record as markdown: /tools/lifesi-genesis-mcp/flocks-createjointoken.md
What flocks_createJoinToken does on Genesis
AI agents use flocks_createJoinToken to create or update resources in Genesis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Genesis environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | Yes |
Parameters from the server's own tool schema.
Why flocks_createJoinToken is rated Medium
An AI agent can call flocks_createJoinToken faster than any human can review: one bad instruction and it creates or modifies resources in Genesis by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (body) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs flocks_createJoinToken safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For flocks_createJoinToken, this is the rule to start with:
flocks_createJoinToken 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 Genesis, apply this rule, and every flocks_createJoinToken call is checked against it from then on.
Questions about flocks_createJoinToken
Create an org-scoped single-use join token (admin required) (POST /v1/flocks/byom/tokens) [service status: not_deployed]. It is categorised as a Write tool in the Genesis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
flocks_createJoinToken accepts 1 parameter: body. Required: body. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for flocks_createJoinToken: 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 Genesis. Nothing to install.
flocks_createJoinToken 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 flocks_createJoinToken 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 flocks_createJoinToken. 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.
flocks_createJoinToken is provided by the Genesis MCP server (@lifesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue