How to control what AI agents do
Plain answers for the people putting AI agents into production and the people who sign off on them: how to stop a tool call before it runs, what one agent's key should be allowed to do, and how you will know what happened. Each post answers one question.
How do you stop an AI agent's tool call before it runs?
Put the decision outside the AI. Verosek checks what an agent tries to do against the rules you set, lets the allowed actions through, stops the rest and keeps a sealed record of every decision.
The other 5 posts
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.
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.
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.
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.
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.
See it on the product pages

