root@amaltsev >:~/blog$ grep -l "security" -r ~/blog
8 posts on security.
root@amaltsev >:~/blog$ grep -l "security" -r ~/blog
Every step is in scope. The chain is a bulk data export to an external recipient. The agent executes them in order, because the task it was given was "produce a customer report".
A policy has a test suite. The tests pass. Then someone finds an input that gets through, and the retrospective is always the same shape.
There is a question most governance frameworks never ask, because it does not come up until an agent can write code, configure integrations or modify its own workflows.
The trust list has an entry that says delete_user is allowed. What the agent calls is delete_user. Same string, two different things.
Three agents, one platform. The support agent reads the CRM, opens tickets, and refunds up to fifty dollars.
A tool is described by a JSON schema: its parameters, their types, what it accepts. This vocabulary fits an interface.
Almost every comparison of agent security tools lines up vendors on a feature grid and lets the reader decide.
An agent produces a perfectly acceptable response and then sends the wrong payment, deletes the wrong resource, modifies the wrong record, or calls a tool with a mutated argument.
~/blog: 8 matches
root@amaltsev >:~/blog$ cd ~/blog && ls -la
The whole directory is one click away. Every post, filed by subject.
Four channels, all of them read. Pick the one that suits the question.
Where to start: a short question goes to Telegram, a brief goes to email.
No match.