create_workspace_api
MCP server · The governed passthrough
POSTs to one workspace route under your own grant, with the same manifest, the same refusals and the same consent gate as the read door. Anything that ends at a consent screen or is a human ceremony is refused with the reason.
What it needs
| Argument | Type | Required | Description |
|---|---|---|---|
path | string | Yes | |
body | any | No | |
query | any | No |
What it returns
The route's own JSON response with the status it answered, and which route the call resolved to.
Credential
An app session token, from an authenticated app.ax1om.ai session. Call it with only an API key and you get a plain refusal saying so, rather than a confusing 401.
Network call: yes. The full credential split is on authentication.
Example call
Most readers never write the protocol themselves: the agent does, once the server is connected. Both forms are the same call.
Use the ax1om MCP server.Call create_workspace_api: pOSTs to one workspace route under your own grant, with the same manifest, the same refusals and the same consent gate as the read door.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "create_workspace_api", "arguments": {} }}The arguments object is whatever this tool's own input schema declares. An MCP client reads that schema from the server, so it is the server that answers for the exact shape rather than this page.
Notes
- It is permission parity rather than gate removal: the call runs as you, so your role, your plan entitlements and the agent-compute consent gate all still apply, and an agent can do nothing here that you could not do in the app.