# How to integrate Dock certs MCP with OpenAI Agents SDK

```json
{
  "title": "How to integrate Dock certs MCP with OpenAI Agents SDK",
  "toolkit": "Dock certs",
  "toolkit_slug": "dock_certs",
  "framework": "OpenAI Agents SDK",
  "framework_slug": "open-ai-agents-sdk",
  "url": "https://composio.dev/toolkits/dock_certs/framework/open-ai-agents-sdk",
  "markdown_url": "https://composio.dev/toolkits/dock_certs/framework/open-ai-agents-sdk.md",
  "updated_at": "2026-05-12T10:09:01.376Z"
}
```

## Introduction

This guide walks you through connecting Dock certs to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Dock certs agent that can list all credentials issued this month, delete a credential by its id, create a webhook for credential updates through natural language commands.
This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Dock certs account through Composio's Dock certs MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Dock certs with

- [Claude Agent SDK](https://composio.dev/toolkits/dock_certs/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/dock_certs/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/dock_certs/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/dock_certs/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/dock_certs/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/dock_certs/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/dock_certs/framework/cli)
- [Google ADK](https://composio.dev/toolkits/dock_certs/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/dock_certs/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/dock_certs/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/dock_certs/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/dock_certs/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/dock_certs/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Install the necessary dependencies
- Initialize Composio and create a Tool Router session for Dock certs
- Configure an AI agent that can use Dock certs as a tool
- Run a live chat session where you can ask the agent to perform Dock certs operations

## What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.
Key features include:
- Hosted MCP Tools: Connect to external services through hosted MCP endpoints
- SQLite Sessions: Persist conversation history across interactions
- Simple API: Clean interface with Agent, Runner, and tool configuration
- Streaming Support: Real-time response streaming for interactive applications

## What is the Dock certs MCP server, and what's possible with it?

The Dock certs MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Dock certs account. It provides structured and secure access to your verifiable credentials and decentralized identity management, so your agent can perform actions like issuing credentials, managing API keys, retrieving credential details, and automating webhook notifications on your behalf.
- Instant credential issuance and management: Easily have your agent issue new verifiable credentials, retrieve detailed credential metadata, or delete outdated credentials as needed.
- Secure API key lifecycle management: Direct your agent to create, list, retrieve, or delete API keys, ensuring secure programmatic access for your organization.
- Automated webhook setup and oversight: Let your agent create or delete webhook endpoints, so you can receive real-time event notifications from Dock certs to your own systems.
- Credential retrieval and decryption: Ask your agent to fetch specific credentials by ID, with options for full retrieval if protected by a password, ensuring secure and flexible access.
- Tag and metadata cleanup: Enable your agent to delete obsolete tags or credential metadata, keeping your Dock certs environment organized and up to date.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `DOCK_CERTS_CREATE_API_KEY` | Create API Key | Tool to create an API key. Use when you need to generate a new API key with optional alias and IP allowlist. |
| `DOCK_CERTS_CREATE_WEBHOOK` | Create Webhook | Tool to create a webhook endpoint. Use when you need Dock.io to push event notifications to your service. |
| `DOCK_CERTS_DELETE_API_KEY` | Delete API Key | Tool to delete a specific API key. Use after confirming the API key's ID via list_api_keys. |
| `DOCK_CERTS_DELETE_CREDENTIAL` | Delete Credential | Tool to delete a verifiable credential. Use after confirming the credential is no longer needed. |
| `DOCK_CERTS_DELETE_TAG` | Delete Tag | Tool to delete a specific tag. Use when you have a tag ID and want to permanently remove it. |
| `DOCK_CERTS_DELETE_WEBHOOK` | Delete Webhook | Tool to delete a specific webhook. Use after confirming the webhook's ID via list_webhooks. |
| `DOCK_CERTS_RETRIEVE_API_KEY` | Retrieve API Key | Tool to retrieve details of an API key. Tries single-key endpoint first, then falls back to listing and filtering. |
| `DOCK_CERTS_RETRIEVE_API_KEYS` | Retrieve API Keys | Tool to list all API keys. Use when you need to retrieve all API keys for the authenticated account. |
| `DOCK_CERTS_RETRIEVE_CREDENTIAL` | Retrieve Credential | Tool to retrieve a verifiable credential by its unique ID. If a password was used to persist it, include the same password to decrypt and return the full credential. Otherwise, only metadata is returned. |
| `DOCK_CERTS_RETRIEVE_CREDENTIALS` | Retrieve Credentials | Tool to retrieve a list of credential metadata. Use when you need to collect credential details with optional pagination or filtering after authentication. |
| `DOCK_CERTS_RETRIEVE_DID` | Retrieve DID Document | Tool to retrieve a DID Document by its DID. Use after you have a valid DID to resolve and inspect its DID Document. |
| `DOCK_CERTS_RETRIEVE_REGISTRIES` | Retrieve Revocation Registries | Tool to retrieve a list of revocation registries. Use when you need to list all registries created by the authenticated account with optional pagination and filtering. |
| `DOCK_CERTS_RETRIEVE_WEBHOOK` | Retrieve Webhook | Tool to retrieve a specific webhook's details. Use after confirming you have a valid webhook ID. |
| `DOCK_CERTS_RETRIEVE_WEBHOOKS` | Retrieve Webhooks | Tool to list configured webhooks. Use when you need to retrieve all webhook endpoints configured for your account. |
| `DOCK_CERTS_VERIFY` | Verify Credential or Presentation | Tool to verify a verifiable credential or presentation. Use after receiving a credential or presentation from an issuer. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Dock certs MCP server is an implementation of the Model Context Protocol that connects your AI agent to Dock certs. It provides structured and secure access so your agent can perform Dock certs operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Composio API Key and OpenAI API Key
- Primary know-how of OpenAI Agents SDK
- A live Dock certs project
- Some knowledge of Python or Typescript

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.

### 2. Install dependencies

Install the Composio SDK and the OpenAI Agents SDK.
```python
pip install composio_openai_agents openai-agents python-dotenv
```

```typescript
npm install @composio/openai-agents @openai/agents dotenv
```

### 3. Set up environment variables

Create a .env file and add your OpenAI and Composio API keys.
```bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com
```

### 4. Import dependencies

What's happening:
- You're importing all necessary libraries.
- The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Dock certs.
```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
```

### 5. Set up the Composio instance

No description provided.
```python
load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
```

```typescript
dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
```

### 6. Create a Tool Router session

What is happening:
- You give the Tool Router the user id and the toolkits you want available. Here, it is only dock_certs.
- The router checks the user's Dock certs connection and prepares the MCP endpoint.
- The returned session.mcp.url is the MCP URL that your agent will use to access Dock certs.
- This approach keeps things lightweight and lets the agent request Dock certs tools only when needed during the conversation.
```python
# Create a Dock certs Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["dock_certs"]
)

mcp_url = session.mcp.url
```

```typescript
// Create Tool Router session for Dock certs
const session = await composio.create(userId as string, {
  toolkits: ['dock_certs'],
});
const mcpUrl = session.mcp.url;
```

### 7. Configure the agent

No description provided.
```python
# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Dock certs. "
        "Help users perform Dock certs operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
```

```typescript
// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Dock certs. Help users perform Dock certs operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
```

### 8. Start chat loop and handle conversation

No description provided.
```python
print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

// Simple CLI
const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: 'You: ',
});

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

  if (!text) {
    rl.prompt();
    return;
  }

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
```

## Complete Code

```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["dock_certs"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Dock certs. "
        "Help users perform Dock certs operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['dock_certs'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Dock certs. Help users perform Dock certs operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

  // Simple CLI
  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: ',
  });

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

    if (!text) {
      rl.prompt();
      return;
    }

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

main().catch((err) => {
  console.error('Fatal error:', err);
  process.exit(1);
});
```

## Conclusion

This was a starter code for integrating Dock certs MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Dock certs.
Key features:
- Hosted MCP tool integration through Composio's Tool Router
- SQLite session persistence for conversation history
- Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

## How to build Dock certs MCP Agent with another framework

- [Claude Agent SDK](https://composio.dev/toolkits/dock_certs/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/dock_certs/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/dock_certs/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/dock_certs/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/dock_certs/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/dock_certs/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/dock_certs/framework/cli)
- [Google ADK](https://composio.dev/toolkits/dock_certs/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/dock_certs/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/dock_certs/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/dock_certs/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/dock_certs/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/dock_certs/framework/crew-ai)

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.
- [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines.
- [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.
- [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code.
- [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows.
- [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights.
- [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews.
- [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease.
- [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Dock certs MCP?

With a standalone Dock certs MCP server, the agents and LLMs can only access a fixed set of Dock certs tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Dock certs and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Dock certs tools.

### Can I manage the permissions and scopes for Dock certs while using Tool Router?

Yes, absolutely. You can configure which Dock certs scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Dock certs data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)