callev2

Execution boundaries

This customer-facing Skill uses production services only: MCP at https://seleven-mcp-sg.airudder.com/mcp/openagent_oauth and API at https://api.heycall-e.com. Use these fixed targets without asking the user to select an environment. Validate existing connection/configuration metadata against the selected target; if it points elsewhere, stop and explain the configuration mismatch. Do not send credentials there, silently rebind them, or redirect an existing call to production.

Business operations use only MCP tools actually exposed by the host or direct HTTPS through a trusted tool/runtime with secure credential injection. Do not use a business CLI, business SDK, shell command, subprocess, or terminal MCP proxy to make business requests. Do not install clients, dependencies, or helper proxies.

Never invoke the legacy CALL-E MCP tools plan_call, run_call, or get_call_run, including host-prefixed names and aliases for those tools. This applies to preparation, execution, read-only checks, queries, and recovery, even when the tools are exposed. Discovery may list them as prohibited; do not invoke them indirectly through another transport. Use the current Preparation/Call workflow under the MCP tool policy. Missing current tools does not permit a legacy fallback; missing cards alone does not block start_call.

For MCP connection management, reuse a suitable existing connection and prefer the current host's exposed native management tools, APIs, or permitted settings interface. When those are unavailable to the Agent, the current host's already-installed official MCP management commands may handle the connection lifecycle under the connection guidance. Use Codex's own capabilities in Codex, Claude Code's in Claude Code, and the actual supported mechanism in other hosts. This exception does not override an explicit user no-CLI restriction or a host permission denial.

API credential setup and Skill version checks, downloads, installation, and updates use existing non-CLI host facilities. The MCP management exception does not allow command-line HTTP requests, arbitrary scripts, manual OAuth clients, or downloaded installers. If no permitted capability can complete a step, explain the specific gap and ask the user to complete only that step.

Installing the Skill does not connect an account or authorize dialing. A generic request to "test" permits only read-only checks already authorized by the user; an explicit request to place a test call authorizes only that call.