When there is no rule, the answer is no
When an AI agent asks Verax for something there is no rule for, the answer is no. Nothing is allowed by default. That covers the obvious case, like an agent trying to export your customer list. It also covers a quieter one. The agent gets refused, then tries the same thing under a different tool name. A new name has no rule either, so it gets refused again. What that looks like in the policy The…
When an AI agent requests something from Verax that lacks a specific rule, the system defaults to denying the request. This applies to clear instances, such as an agent attempting to export a client database. It also extends to subtler cases, where an agent is denied a request, then tries the same action under a different tool name.
Since this new name lacks a corresponding rule, it too is refused. The policy Verax operates from outlines four tools and nothing else: version 1, default deny, and four rules involving memory.get, memory.put, audit.explain, and message.read. Any other tool name results in an immediate refusal before it reaches the server hosting the tool.
Two rules for the same tool are also denied when the policy is loaded, preventing a second rule from subtly broadening the first. Refusals are documented in the same manner as approvals, noting the agent, tool, and timestamp. In the event of an error, the blocked attempts provide more insight than the successful ones. The record remains on the user's machine and is verified by verax verify, which checks the number of signatures and ensures the chain is unbroken. However, this system does not undergo independent auditing, leaving its integrity unverified.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
