The other 5 posts

[ Field guide ]

How do you secure AI agents?

Limit what each agent can do, decide each action outside the AI model, read what it reads and keep a record you can check. Verosek does all four in one place, so security is not a second vendor.

6 Nov 20267 min read
[ Reference ]

AI gateway, LLM router, MCP gateway, AI firewall: what is the difference?

A router picks the model, an AI gateway controls who may use it, a firewall reads the words, and an MCP gateway decides each tool call before it runs. Who needs which, and how Verosek does them on one key.

6 Nov 20266 min read
[ Field guide ]

What is prompt injection, and what actually stops it?

Prompt injection is text that makes a model follow the attacker. No filter catches all of it, so the control that holds sits outside the model: a rule on the tool call. Verosek decides that call before it runs.

6 Nov 20264 min read
[ Benchmark ]

Eight AI model setups, 19 MCP attack tasks: how often did the model try to leak a planted secret?

Self-reported: a lower bound of 22.7 to 61.0, and 9 to 18 of 19 tasks fired, on one run per route. Assay's results, limits kept. They rank these configurations, not the models, and say nothing about any gateway.

6 Nov 20266 min read
[ Field guide ]

How do you restrict what SQL an AI agent can run?

Check each statement against rules set outside the AI. Verosek lets through what the agent's key allows and refuses the rest, with the reason, before the database sees it.

6 Nov 20265 min read
[ In the product ]

See it on the product pages

Rules for every tool call Verosek runs. Decided before it executes, outside the model.

Still curious? Ask your favourite AI about Verosek.