Skip to content

mcp-security.md

Latest commit

 

History

History
108 lines (82 loc) · 3.75 KB

mcp-security.md

File metadata and controls

108 lines (82 loc) · 3.75 KB
Raw

MCP Security Best Practices

Understanding MCP security

MCP servers extend Kiro's capabilities by connecting to external services and APIs. Since all MCP servers are third-party code, this introduces potential security considerations:

  • Access to sensitive information: MCP servers may require API keys or tokens
  • External code execution: MCP servers run code outside of Kiro's sandbox
  • Data transmission: Information flows between Kiro and external services
  • Source verification: Review the source code and verify the server comes from a trusted source before using
  • Isolation: Run servers in isolated environments when possible and limit the permissions granted

Secure configuration

Protecting API keys and tokens

  1. Never commit configuration files with sensitive tokens to version control
  2. Create tokens with minimal permissions necessary for the MCP server to function
  3. Limit access scope to only the repositories or resources needed
  4. Regularly rotate API keys and tokens used in configurations
  5. Use environment variables when possible instead of hardcoding values

Example: Using environment variables

{
  "mcpServers": {
    "github": {
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}"
      }
    }
  }
}

Approved environment variables

For security, Kiro only expands environment variables that are explicitly approved. When you add or modify an MCP server configuration that includes unapproved environment variables, Kiro displays a security warning popup.

To manage approved environment variables:

  1. Open Kiro settings
  2. Search for "Mcp Approved Env Vars"
  3. Add the environment variables you want to allow for expansion

Configuration file permissions

# Set restrictive permissions on user-level config
chmod 600 ~/.kiro/settings/mcp.json

# Set restrictive permissions on workspace-level config
chmod 600 .kiro/settings/mcp.json

Safe tool usage

Tool approval process

  1. Review each tool request carefully before approval
  2. Check the parameters being passed to the tool
  3. Understand what the tool will do before approving it
  4. Deny any suspicious requests that don't match your current task

Auto-approval guidelines

Only auto-approve tools that:

  1. Don't have write access to sensitive systems
  2. Come from trusted sources with verified code
  3. Are used frequently in your workflow
  4. Have limited scope of what they can access

Workspace isolation

Use workspace-level configurations for project-specific MCP servers to ensure:

  • MCP servers only run when working in the relevant project
  • Tokens and configurations are isolated between projects
  • Security risks are contained to specific workspaces

Monitoring and auditing

Checking MCP logs

  1. Open the Kiro panel
  2. Select the Output tab
  3. Choose "Kiro - MCP Logs" from the dropdown

Auditing tool usage

  • Check your MCP configuration for auto-approved tools
  • Review the MCP logs for tool usage patterns
  • Monitor server activity for unexpected behavior
  • Remove auto-approval for tools you no longer use frequently

Responding to security incidents

If you suspect a security issue with an MCP server:

  1. Disable the server immediately in your configuration
  2. Revoke any tokens or API keys associated with the server
  3. Check for unauthorized activity in the connected services
  4. Report the issue to the MCP server maintainer

Additional security measures

Network security

  1. Use firewalls to restrict outbound connections from MCP servers
  2. Consider using a VPN for sensitive MCP server connections
  3. Monitor network traffic to and from MCP servers

System security

  1. Keep your system updated with security patches
  2. Run MCP servers with minimal privileges
  3. Use separate user accounts for running sensitive MCP servers