Every MCP server tool. Governed by policy.
Declarative rules that control how AI agents cache, reuse, and invalidate tool responses. Glob-pattern matching. First-match-wins resolution. No agent guesswork. Enforced by the Vinkius.
State coherence without a clock.
LLMs have no sense of time. Time-based expiration is meaningless inside a context window. The Vinkius enforces a binary cache vocabulary - no-store or immutable - built on RFC 7234 semantics already embedded in model training data.
no-store
Every call hits the upstream tool. No caching. Use for real-time data - stock prices, live metrics, active deployments. The agent always gets the freshest value.
immutable
Response is cached indefinitely within the session. Use for reference data - schema definitions, configuration constants, API specs. One call, reused everywhere.
invalidate()
Causal invalidation via Redis pub/sub. When upstream data changes, the cache is purged in under 50ms across all connected agents. No stale reads.
First match wins. No ambiguity.
Policies are evaluated in declaration order against tool names using glob patterns. The first matching rule applies. Defaults kick in when nothing matches. Overlap detection warns before it becomes a bug.
Glob-Pattern Matching
Match tool names using glob syntax: db_* matches all database tools, *_read matches read-only operations. Wildcards, character classes, and negation supported.
Default Fallback
When no rule matches a tool, the default policy applies. Configure your organization-wide baseline - no-store for maximum safety, or immutable for maximum efficiency.
Overlap Detection
The engine warns when two rules could match the same tool. Resolve ambiguity before it reaches production. First-match-wins semantics guarantee deterministic behavior.
Response Decoration
Policy metadata is injected into tool responses as MCP annotations. The agent sees cache-control, must-revalidate, and staleness hints - training data it already understands.
AI agents never stop.
MCP Servers need Vinkius.
Autonomous agents don't sleep. Every tool call hits a hardened isolation perimeter - cryptographic lockfiles, zero-trust RBAC, and hard execution quotas enforced at the payload level. No wrappers. Titanium-grade governance for autonomous compute.