Crisis Planner
crisis_plannerGenerates crisis playbooks with response team roles and notification steps for operational crises, tailored to company, industry, customer base, data sensitivity, and compliance needs.
Instructions
Helps you decide who does what when a crisis hits: it takes your company, industry, customer base and data sensitivity, and returns crisis playbooks with a response team and notification steps for each crisis. Name the crises you know of to get those playbooks; without them it uses a default set of common crises for your sector, not ranked by likelihood. Each compliance item you list is used in the notification steps. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of retention_playbook when you need response roles and notification steps for operational crises.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"company": "<company>",
"industry": "<industry>",
"customer_base": "<customer_base>",
"data_sensitivity": "<data_sensitivity>"
},
"name": "crisis_planner"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| company | Yes | Company name. Format is text. For example, "invoice review service". | |
| industry | Yes | Industry affects which crises to prioritize. Format is text using one of the listed labels. For example, "fintech". | |
| your_sector | No | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech". | |
| company_size | No | Affects response team structure. Format is text using one of the listed labels. For example, "startup_under_50". | |
| customer_base | Yes | Customer type affects communication approach. Format is text using one of the listed labels. For example, "b2b_enterprise". | |
| business_model | No | Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. Format is text using one of the listed labels. For example, "saas". | |
| data_sensitivity | Yes | Data sensitivity affects security protocols. Format is text using one of the listed labels. For example, "high_pii_financial". | |
| potential_crises | No | Optional: crisis types to plan for, comma-separated. If not provided, the tool uses a default set of common crises for your sector (not ranked by likelihood). Options: data_breach, service_outage, sla_breach, regulatory_action, fraud_incident, ai_wrong_action, pr_incident, executive_departure, security_vulnerability, customer_data_exposure, product_safety. Format is text. For example, "service outage during month-end close". | |
| compliance_requirements | No | Optional: Relevant compliance, comma-separated (for example ISO 27001, SOC 2, GDPR). Each item is named in the notification steps. Format is text. |