Establish OrgX session context, discover granted scopes, and get the v2 tool routing map. Also known as: bootstrap, setup, tool routing. USE WHEN: first call in a fresh session, after reconnecting, or before performing a multi-step workflow. NEXT: use orgx_search, orgx_inspect, or orgx_recommend ...
AI agents call orgx_bootstrap to retrieve information from OrgX without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
_context | object | — | Client context for conversation tracking (strongly recommended for cross-client continuity) |
timezone | string | — | Optional user timezone for date-sensitive readouts |
client_name | string | — | Optional MCP client name, such as codex, chatgpt, cursor, or claude |
workspace_id | string | — | Canonical workspace UUID to bind as the active session workspace |
conversation_id | string | — | Optional client conversation/session identifier for continuity |
Parameters from the server's own tool schema.
Even though orgx_bootstrap only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (21 properties)
Documented attack patterns abuse exactly the kind of access orgx_bootstrap gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OrgX, and nothing reaches the server without passing your rules. This is the rule we recommend for orgx_bootstrap:
{
"version": "1",
"default": "deny",
"tools": {
"orgx_bootstrap": {}
}
}orgx_bootstrap is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Establish OrgX session context, discover granted scopes, and get the v2 tool routing map. Also known as: bootstrap, setup, tool routing. USE WHEN: first call in a fresh session, after reconnecting, or before performing a multi-step workflow. NEXT: use orgx_search, orgx_inspect, or orgx_recommend based on the returned routing map. DO NOT USE WHEN: you already have session context and need to read or mutate work. Read-only. It is categorised as a Read tool in the OrgX MCP Server, which means it retrieves data without modifying state.
orgx_bootstrap accepts 5 parameters: _context, timezone, client_name, workspace_id, conversation_id. The full parameter table on this page comes from the server's own tool schema.
Register the OrgX MCP server in PolicyLayer and add a rule for orgx_bootstrap: 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 OrgX. Nothing to install.
orgx_bootstrap is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the orgx_bootstrap 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 orgx_bootstrap. 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.
orgx_bootstrap is provided by the OrgX MCP server (useorgx/orgx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 OrgX tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 OrgX tools catalogued and risk-classified — across an index of 42,500+ MCP servers.