> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runlayer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Responding to Discoveries

> Security team framework for handling discovered shadow MCP servers and skills

When Detect identifies shadow servers or skills, follow this response framework to assess risk and take appropriate action.

## Triage by Risk Level

### Shadow MCP Servers

The Runlayer dashboard categorizes discovered shadow servers as **Managed Available** (a matching Runlayer connector exists) or **New Server** (no matching connector). Use these categories alongside the risk assessment framework below to prioritize your response.

| Risk Level   | Indicators                                                                         | Response                                                  |
| ------------ | ---------------------------------------------------------------------------------- | --------------------------------------------------------- |
| **Critical** | Unknown/suspicious source, broad permissions, external data exfiltration endpoints | Immediate removal, incident response, credential rotation |
| **High**     | Third-party MCP not already managed in Runlayer, access to sensitive data          | Block via MDM, require security review before approval    |
| **Medium**   | Known vendor but not approved, limited scope                                       | User education, migrate to Runlayer-managed version       |
| **Low**      | Known safe MCP, read-only access, internal only                                    | Document and monitor, encourage migration to Runlayer     |

### Shadow Skills

| Risk Level  | Indicators                                                                                    | Response                                         |
| ----------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------ |
| **High**    | Risky instructions detected — prompt injection, data exfiltration patterns, unsafe automation | Immediate removal, investigate source repository |
| **Medium**  | Potentially risky characteristics that warrant review                                         | Security review, verify skill source and intent  |
| **Low**     | Minor concerns, unlikely to pose a threat                                                     | Monitor, encourage migration to managed skill    |
| **Minimal** | No concerning patterns detected                                                               | Document and track                               |

## Investigation Checklist

<AccordionGroup>
  <Accordion title="Gather Context">
    1. Identify the user and their role
    2. Determine when the MCP or skill was configured/installed
    3. Review the stated purpose and actual capabilities
    4. Check if the MCP connects to external endpoints
    5. Assess what data the MCP or skill could access
  </Accordion>

  <Accordion title="Evaluate MCP Server Source">
    * Is it from a known vendor (GitHub, Slack, etc.)?
    * Is it an open-source project? Check repository activity and maintainers
    * Is it internally developed? Verify with the development team
    * Are there any known vulnerabilities or security advisories?
  </Accordion>

  <Accordion title="Evaluate Skill Source">
    * Is the skill from a trusted, known repository?
    * Does the skill contain instructions that could manipulate AI behavior (prompt injection)?
    * Does the skill instruct the AI to send data to external endpoints?
    * Is the skill a community skill or internally developed?
    * Does the skill's scope match the user's legitimate needs?
  </Accordion>

  <Accordion title="Determine Business Need">
    * Does the user have a legitimate business reason?
    * Could an existing Runlayer-managed MCP or skill fulfill the need?
    * Is this a one-off or widespread usage pattern?
  </Accordion>

  <Accordion title="Remediation Options">
    * **Migrate**: Help user set up equivalent Runlayer-managed MCP or skill
    * **Approve**: Submit for formal review and add as a managed connector
    * **Remove**: Use MDM to remove configuration from device
    * **Block**: Add to blocklist if risky or prohibited
  </Accordion>
</AccordionGroup>

## Response Workflow

```mermaid theme={null}
flowchart TD
    A[Shadow Discovery Detected] --> B{Server or Skill?}

    B -->|Server| C{Assess Server Risk}
    C -->|Critical| D[Immediate Response]
    C -->|High| E[Security Review]
    C -->|Medium| F[User Outreach]
    C -->|Low| G[Monitor & Document]

    D --> D1[Remove from device]
    D --> D2[Incident response]
    D --> D3[Credential rotation]

    E --> E1[Block via MDM]
    E --> E2[Require approval]

    F --> F1[Educate user]
    F --> F2[Migrate to managed]

    G --> G1[Add to inventory]
    G --> G2[Encourage migration]

    B -->|Skill| H{Assess Skill Risk}
    H -->|High| I[Remove & Investigate]
    H -->|Medium| J[Security Review]
    H -->|Low/Minimal| K[Monitor & Document]

    I --> I1[Remove skill from device]
    I --> I2[Review source repository]

    J --> J1[Verify skill instructions]
    J --> J2[Approve or block]

    K --> K1[Track in inventory]
    K --> K2[Encourage managed skill]
```

## Related Resources

<CardGroup cols={2}>
  <Card title="Security Best Practices" icon="lock" href="/mcp-security-best-practices">
    Comprehensive MCP security guidelines and threat prevention
  </Card>

  <Card title="Audit Logs" icon="list" href="/platform-audit-logs">
    View detailed activity logs for investigations
  </Card>
</CardGroup>