Concepts
MCP Gateway
botYguard supports MCP-connected agents that need governed access to tools and integrations. Instead of giving an external agent direct access to credentials or unrestricted tools, route the connection through botYguard.
When To Use MCP
Use MCP when you are connecting an existing agent, developer tool, or agent runtime that botYguard does not host directly. The external client connects through a botYguard MCP API key or connector URL.
Use hosted agents when you want botYguard to manage the agent runtime for a specific use case.
Gateway Controls
MCP gateway controls help teams:
- identify the agent, profile, provider, role, and expiration
- scope access with policy before tools are reached
- keep provider secrets and integration credentials out of external instructions
- audit the requested action, policy result, and downstream tool usage
- rotate or expire connectors when access should end
Connection Model
- Create or select a botY profile.
- Generate an MCP API key or pre-authorized connector URL.
- Assign the profile, provider, role, and expiration.
- Add the MCP credential to the external agent client.
- Use policy assignments to decide what the agent may access.
Security Notes
Do not paste provider secrets, Google refresh tokens, Discord tokens, or botYguard admin credentials into external agent prompts. The MCP connection should route through botYguard so approved access can be scoped, logged, and revoked.