From 57b45d7a5faba8c2346c524cfe8c20af64a6e470 Mon Sep 17 00:00:00 2001 From: Albert Mavashev Date: Wed, 25 Mar 2026 13:02:58 -0400 Subject: [PATCH] updated dates updated dates --- ...for-ai-agents-why-every-tool-call-needs-a-policy-decision.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/zero-trust-for-ai-agents-why-every-tool-call-needs-a-policy-decision.md b/blog/zero-trust-for-ai-agents-why-every-tool-call-needs-a-policy-decision.md index d3f16d9..30966d0 100644 --- a/blog/zero-trust-for-ai-agents-why-every-tool-call-needs-a-policy-decision.md +++ b/blog/zero-trust-for-ai-agents-why-every-tool-call-needs-a-policy-decision.md @@ -1,6 +1,6 @@ --- title: "Zero Trust for AI Agents: Why Every Tool Call Needs a Policy Decision" -date: 2026-03-25 +date: 2026-03-24 author: Cycles Team tags: [security, zero-trust, agents, MCP, OWASP, production, tool-calling, governance] description: "Microsoft, Cisco, and OWASP converged on one conclusion: AI agents need zero trust at the tool-call layer. What changed and how to enforce it."