> ## Documentation Index > Fetch the complete documentation index at: https://docs.apexgenius.ai/llms.txt > Use this file to discover all available pages before exploring further. # MCP Tool Reference > How ApexGenius discovers and runs operations for Salesforce and connected apps. The default ApexGenius connector at `/mcp` always exposes three tools. It does not place every Salesforce, Jira, n8n, HQ Rental, Google, or social definition into the AI client's context. | Public tool | What it does | | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `apex_search_tools` | With an empty query, lists the active and healthy providers connected to the account and their read/write operation counts. With a task query, returns only the best matching inner tool names, descriptions, input schemas, and risk annotations. | | `apex_call_read_tool` | Runs an exact read-only inner operation returned by discovery. It rejects writes and operations that are no longer healthy, connected, enabled, or authorized. | | `apex_call_write_tool` | Runs an exact write operation returned by discovery. Writes pass current policy and audit controls. Compatible clients can ask the user to confirm a risk-labeled write before execution. | The effective inner catalog is calculated for every account. Salesforce operations are always namespaced with `salesforce_`. Other operations use their provider namespace, such as `jira_`, `confluence_`, `n8n_`, and `hqrental_`. Disabled operations do not appear in discovery, and a client holding an old cached name cannot bypass the current catalog. Every Salesforce call checks ApexGenius authorization. New per-user connections apply the connected user's Salesforce permissions. Some existing projects still use a project-level shared connection, so confirm the connection mode shown for the selected Salesforce project before relying on a user-specific permission boundary. ## Salesforce operations Discovery can return these 21 namespaced Salesforce operations. ### Project and metadata discovery | Operation | What it does | | -------------------------- | ----------------------------------------------------------------------------------------- | | `salesforce_list_projects` | List project keys, names, organizations, and sandbox indicators available to the account. | ### Queries, records, and schema | Operation | What it does | | ----------------------------------- | --------------------------------------------------------------------------------------------------------------- | | `salesforce_query_soql` | Run task-specific SOQL and return selected Salesforce fields. | | `salesforce_create_record` | Create one Salesforce record with supplied field values. | | `salesforce_update_record` | Update selected fields on one existing Salesforce record. | | `salesforce_delete_record` | Delete one Salesforce record by ID. | | `salesforce_get_record` | Retrieve one Salesforce record by object type and record ID. | | `salesforce_search_records` | Search records with SOSL for the selected project. | | `salesforce_list_objects` | List accessible Salesforce objects, optionally limited to queryable or custom objects. | | `salesforce_describe_object` | Return describe details for one object, including fields, types, picklists, and relationships. | | `salesforce_execute_anonymous_apex` | Execute supplied anonymous Apex. The code can change or delete Salesforce data and perform configured callouts. | ### Staging and documentation The MCP filesystem covers private Salesforce staging and project documentation. Chat-session storage is not available through these operations. | Operation | What it does | | -------------------------------- | -------------------------------------------------------------------------------------------- | | `salesforce_read_file` | Read a bounded range from one staged Salesforce metadata or Markdown documentation file. | | `salesforce_write_file` | Create or overwrite a Salesforce metadata component or Markdown document in private staging. | | `salesforce_edit_file` | Replace exact matching content in one staged metadata component or document. | | `salesforce_delete_file` | Permanently delete one staged metadata or documentation file. | | `salesforce_list_files` | List staged metadata or documentation files using an optional folder or pattern filter. | | `salesforce_grep` | Search staged file names or content. | | `salesforce_list_live_metadata` | List components of one supported metadata type directly from the selected org. | | `salesforce_get_live_component` | Retrieve one live component into private staging when it is not already present. | | `salesforce_deploy` | Deploy selected staged files with the requested test level. | | `salesforce_check_deploy_status` | Read status and details for a deployment ID. | | `salesforce_cancel_deploy` | Cancel an in-progress deployment. | ## Jira and Confluence Jira and Confluence operations become discoverable only when their provider row is active, the user's connection is active and healthy, the account has effective access, and the operation is enabled. The current schemas for both providers require an authorized ApexGenius `project_id` on every operation so the gateway can verify project and organization access. Jira is still Beta and can also require project activation during the current transition. The connected Atlassian account remains the Jira and Confluence content boundary. Jira currently supplies 15 issue, user, field, sprint, and project operations. Confluence supplies six space and page operations. Reads and writes carry distinct risk annotations, and writes pass the same tool-policy and write-audit path as the rest of the gateway. ## n8n A connected n8n provider makes its current 20 operations available to discovery, subject to the connection, account, authorization, and tool-policy checks described above. These operations include workflow inspection, templates, generation, replacement, autofix, test runs, data tables, instance audit, and deletion. The public ApexGenius surface remains three tools. ## Other connected apps HQ Rental, Google services, social publishers, remote MCP providers, and approved custom MCP servers use the same public discovery and read/write call tools. An implementation appearing in the catalog does not mean an account is connected. Discovery returns an operation only when the provider and connection pass their live availability checks. ## Guardrails * **Authorization per call:** cached names cannot bypass the current provider, connection, resource, surface, or tool-policy checks. * **Read/write boundary:** the read proxy rejects writes. The write proxy is statically labeled destructive and open-world so MCP clients can apply their write confirmation behavior. * **Confirmation and audit:** writes are risk-labeled so compatible clients can request confirmation. Supported provider writes are recorded in the write audit. A universal server-enforced Auto, Ask, or Off mode is not yet part of the public contract. * **Health gating:** inactive provider rows and unhealthy or inactive connections disappear from discovery and are denied at execution. * **Rate limits:** weighted sliding-window limits protect the gateway and connected provider quotas. * **Content-minimized logging:** operational records retain bounded tool, actor, project, timing, count, size, outcome, and error-code metadata, not generic copies of tool arguments or results. See [How the MCP connection works](../concepts/how-mcp-works) and the [Privacy Policy](https://www.apexgenius.ai/privacy). * **Restricted data:** do not use these tools for payment-card data, PHI, government identifiers, passwords, API keys, MFA codes, or other authentication secrets.