report_compliance
Marks memories injected in a previous session as followed, violated, or unknown with optional evidence, then returns updated/total counts so agents can verify compliance reports were stored.
Instructions
Report compliance for a previous injection session returned by session_start. Call this to mark which injected memories were followed or violated, with optional evidence. Reports are processed item by item: a bad item is logged and skipped while the call still succeeds, so the response's updated/total counts must be checked rather than assuming all reports were stored. Requires a compliance-enabled server; no agent API key is required by this tool.
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": {
"inject_session_id": "<inject_session_id>",
"reports": "<reports>"
},
"name": "report_compliance"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | API key for agent authentication (required if agent has a registered key) | |
| reports | Yes | List of compliance reports, one per memory | |
| agent_id | No | ID of the agent reporting compliance | unknown |
| inject_session_id | Yes | The inject_session_id from a previous session_start call |