Menu

Post image 1
Post image 2
1 / 2
0

What Pipelock Inspects, And What Tool Policy Inspects Instead

DEV Community·Josh Waldrep·23 days ago
#dVE0J0HJ
#security#ai#tool#wire#layer#agent
Reading 0:00
15s threshold

A wire-only proxy scans wire bytes. Opaque media bytes pass through the wire layer untouched. Anyone evaluating an agent firewall should know which class of attacks gets caught at which layer, because pretending the wire layer covers everything is the wrong sales pitch and the wrong mental model. This post is the layer split. Pipelock has two inspection layers that operate at different abstraction levels, and the marketing-friendly claim "we scan everything" is true for some shapes of attack and false for others. Saying so plainly is more useful to a buyer than saying nothing. The wire layer Pipelock's wire layer scans bytes as they cross the proxy. Every transport Pipelock supports gets the same set of scanners: HTTP forward proxy. CONNECT and absolute-URI requests, request and response bodies on intercept paths, headers on every transport. MCP stdio. JSON-RPC frames on the subprocess pipe, both directions. MCP HTTP and SSE.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More