start_session
Create an engagement session by collecting program details, scope, rules, and authorization before sending any traffic.
Instructions
FIRST TOOL. Ask the user for every field before creating an engagement session; this sends no traffic.
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": {
"program_name": "<program_name>",
"in_scope": "<in_scope>",
"out_of_scope": "<out_of_scope>",
"rules": "<rules>",
"allowed_activities": "<allowed_activities>",
"forbidden_tests": "<forbidden_tests>",
"authorization_confirmed": "<authorization_confirmed>"
},
"name": "start_session"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rules | Yes | ||
| in_scope | Yes | ||
| out_of_scope | Yes | ||
| program_name | Yes | ||
| forbidden_tests | Yes | ||
| allowed_activities | Yes | ||
| authorization_confirmed | Yes | ||
| max_requests_per_second | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||