WEBVTT

1
00:00:00.000 --> 00:00:01.760
No credential warning appeared.

2
00:00:01.936 --> 00:00:04.800
Does that mean the whole payload was inspected?

3
00:00:05.040 --> 00:00:08.480
If the payload exceeded a scan limit, those are two different

4
00:00:08.549 --> 00:00:09.040
things.

5
00:00:09.320 --> 00:00:12.880
A useful monitoring system should make that gap visible.

6
00:00:13.431 --> 00:00:17.031
Agent tools can produce very large arguments and outputs.

7
00:00:17.271 --> 00:00:21.511
ClawMetry keeps credential inspection bounded so one

8
00:00:21.575 --> 00:00:24.711
oversized payload cannot consume unlimited work.

9
00:00:24.911 --> 00:00:28.711
The important part is telling you when that bound was reached.

10
00:00:29.238 --> 00:00:33.398
When a tool payload exceeds the bounded credential scan, ClawMetry

11
00:00:33.455 --> 00:00:37.158
raises an informational inspection incomplete finding.

12
00:00:37.371 --> 00:00:40.998
It records the number of limited payloads and the reasons.

13
00:00:41.098 --> 00:00:44.038
The contents do not need to be copied into the finding.

14
00:00:44.576 --> 00:00:48.416
In the checked example, an oversized command argument produces an

15
00:00:48.467 --> 00:00:50.176
informational coverage finding.

16
00:00:50.469 --> 00:00:53.696
An ordinary Git status argument stays quiet.

17
00:00:53.856 --> 00:00:58.336
This is evidence about the inspection boundary, not evidence that

18
00:00:58.376 --> 00:01:00.736
the oversized payload was malicious.

19
00:01:01.284 --> 00:01:05.044
Find the relevant tool activity and review the part of the workflow

20
00:01:05.108 --> 00:01:07.364
that produced the oversized content.

21
00:01:07.564 --> 00:01:11.844
Use an appropriate controlled review or a smaller input to

22
00:01:11.878 --> 00:01:14.964
answer the question the bounded scan could not settle.

23
00:01:15.124 --> 00:01:19.204
Keep the coverage gap visible until you have that evidence.

24
00:01:19.742 --> 00:01:23.102
Make inspection incomplete visible in your agent workflow.

25
00:01:23.322 --> 00:01:27.422
See the finding, understand the reason, and review what happened

26
00:01:27.518 --> 00:01:27.982
next.

27
00:01:28.142 --> 00:01:31.662
Explore this detector at ClawMetry dot com.
