Agents Told That Failed Attempts Are Audited
The MCP documentation and the agent skill now state that a rejected tool call is recorded in the project's audit log, so an agent has a reason not to retry a vault key the user has not confirmed.
#What's Changed
- [Improvement] The MCP vault key attempt limits section now explains that rejected attempts are recorded, not silent: a failed tool call lands in the project's audit log with its status, error code, acting user and reported client name, filed under the action attempted. The advice not to retry a rejected vault key previously rested on the throttle alone.
- [Improvement] The ApiVault agent skill carries the same note across SKILL.md, README.md and the CLI and MCP references, and is re-synced to the copies bundled in the website and MCP server repositories.
- [Improvement] Request logging no longer parses the body of a failed response it is about to discard. Entries are stored per project, so a rejection that never resolved one — an unauthenticated call, the most common rejection on a public endpoint — now skips that work.