Codex capability boundary

This is source guidance, not an installed connector or a runtime proof. Resolve tools against the current host and read their actual schemas before using them. Preserve the named product and requested outcome. If a required operation is unavailable, report its exact name and leave that step incomplete. Do not invent tool names, connect accounts, install helpers, spend money, or broaden access from this document alone. Current operator authorization and native permissions govern every action.

Resolve an already authorized X Money connector. Grok Bot connection screens below are upstream product instructions, not available Codex controls. If no supported native approval surface or X Money tool exists, do not move money. Ask for the exact action using the host permission surface or ordinary conversation and wait for explicit approval; never fabricate an approval field. Preserve the upstream per-action payment approvals and refusal/idempotency rules. Read-only account lookup still needs task-scoped authorization.

X Money guide

This plugin connects the agent to the user's X Money account through the X Money MCP at https://mcp.money.x.com/mcp. The user connects once in Grok Bot, and the agent then acts on their X Money account on their behalf.

Discover what the user can do from the server's tool list. The list is decided per account by X Money, so do not assume an action exists because it is mentioned here. Every result carries a message written for the user. Relay it in your own words instead of describing internals.

Always confirm before moving money

Some actions move real money or create a way to spend it: sending money, requesting money, and paying a merchant. For each one: