Amazon introduced a pattern for securing multi-tenant AI agents by ensuring that RAG search queries are scoped to specific users. The solution uses ACL-aware knowledge bases combined with a request interceptor in the AgentCore Gateway to deterministically inject verified user identities into tool calls, preventing LLMs or prompt injections from accessing unauthorized data.
Amazon introduced a serverless Model Context Protocol (MCP) gateway built on Amazon ECS Fargate that allows AI agents to query enterprise data lakes using a metadata-driven approach. Instead of writing custom integration code for every new dataset, you define table schemas and business logic in JSON, which the system automatically registers and indexes.
Amazon introduced Web Answer on Bedrock AgentCore, a managed tool that simplifies agent-based web research. It automates the entire pipeline from searching and verifying facts to synthesizing cited answers, delivering results via MCP.
Microsoft launched new security features to manage AI agent risks, including Dynamic Permissions for task-scoped authority and Microsoft Execution Containers (MXC) for OS-level isolation. The update also adds local AI agent and MCP configuration discovery to Microsoft Defender for Windows and macOS.
Mistral AI has launched significant updates to Mistral Studio, a platform designed to take AI projects from pilot to production. It now includes managed agents, advanced workflow orchestration, and enterprise-grade observability, enabling deployment across cloud, VPC, or on-premises environments.
NVIDIA has introduced the AI Factory Operations Agent, a framework built on NemoClaw and OpenShell, designed to automate the management and troubleshooting of large-scale GPU clusters. By leveraging specialized sub-agents and Model Context Protocol (MCP), it enables SREs to perform root cause analysis across hardware, network, and software layers through a unified chat interface.
This update outlines a method for building a semantic knowledge base directly within PostgreSQL using the AIDB extension. By indexing schema metadata and utilizing the Model Context Protocol (MCP), you can expose database tools to agents in Amazon Bedrock AgentCore while enforcing existing row-level security.
Amazon has updated the AgentCore Gateway to support automated token exchange between Microsoft Entra ID and protected REST APIs. By leveraging this flow, AI agents can now perform actions in platforms like ServiceNow using the identity and permissions of the end-user rather than acting as a generic service account.
MoEngage successfully integrated over 400 internal REST APIs as agent tools using Amazon Bedrock AgentCore Gateway. This approach eliminated the need for manual MCP server maintenance, complex networking, and security risks associated with public internet exposure.
Google Cloud has released IAM Helper, a suite of agent-facing building blocks designed to automate complex Identity and Access Management (IAM) workflows. By integrating with Google Cloud's core IAM engines via MCP (Model Context Protocol), these tools enable autonomous agents to handle tasks like troubleshooting 403 errors, simulating policy impacts, and requesting just-in-time access.
Amazon Bedrock AgentCore is a new service designed to streamline the deployment and management of multi-agent architectures. It handles agent hosting, secure tool access via MCP, and session isolation, enabling teams to focus on agent behavior rather than operational overhead.
AWS announced general availability of training sessions within Amazon SageMaker AI serverless model customization. Teams can write their own post-training loops — including custom loss functions and reward signals for reinforcement learning — while SageMaker AI handles GPU allocation, distributed execution, fault recovery, and checkpoint storage. Supported techniques include SFT, DPO, RLVR, RLAIF, and multi-turn RL, and users can choose LoRA or full fine-tuning. The feature supports models including gpt-oss-20b, gemma-4-31B-it, Qwen3.6-27B, and Qwen3.8-27B, and billing is based on tokens processed, pausing while a user's reward function scores responses.
Google announced Public Preview of streaming support in API Gateway, covering Server-Sent Events, chunked/NDJSON responses, WebSockets and gRPC streaming. Streaming endpoints can now sit behind the same gateway as regular APIs, keeping existing authentication, logging and monitoring, without any changes to the API spec. Streams can stay open up to one hour, and gateways now get a predictable default hostname instead of a generated hash. The feature also ties into model routing, letting a single gateway stream responses from Gemini, Claude and OpenAI gpt-oss models.
NVIDIA has detailed Sentry, a new security framework that sits outside an AI agent's reach, enforcing policy and watching behavior from a dedicated hardware trust domain on BlueField-4 DPUs. The idea is simple: even if an agent is compromised or goes off-script while using tools and credentials, Sentry keeps watching and can cut it off because it doesn't depend on the host OS the agent runs on. Two components do the work — DOCA Tower, a proxy that inspects and authorizes every agent network request, and DOCA Argus, which reads live memory to understand what's actually running. When something looks wrong, the system can quarantine the agent within milliseconds, without needing the agent or the host to cooperate.
AWS introduced Agent Registry, a managed catalog service for Model Context Protocol (MCP) servers, agents, and agent skills. Instead of hardcoding every tool into an orchestrator, agents can now search an approved, versioned catalog at runtime and build a client from the returned descriptor. A reference sample demonstrates a Discover → Instantiate → Execute loop using Amazon Bedrock AgentCore Gateway and AgentCore runtime, with Anthropic Claude Sonnet as the foundation model.
AWS and Keyfactor published a reference design that fixes a known weak point in Model Context Protocol (MCP) deployments: MCP has no built-in way to authenticate which agent is actually making a request. The architecture adds three trust layers — user-to-system, agent-to-agent, and agent-to-tool-server — built on signed request envelopes, delegation assertions signed by the user, RFC 8693 audience-restricted tokens, and live OCSP revocation checks. A working example runs on Amazon Bedrock and the AWS Strands Agents SDK with Keyfactor EJBCA issuing and validating the X.509 certificates, and the full code is on GitHub.
Microsoft announced an expansion of its Project Perception security framework to address risks from autonomous AI agents, framing them as a new category of 'insider' that needs distinct identity, permission, and risk controls. The update introduces Dynamic Permissions (least-privilege, task-scoped, time-bound access), Dynamic Agent Risk (continuous risk scoring based on behavior drift and context), and Dynamic Conditional Access (graduated responses from narrowing access to full runtime isolation). Microsoft is also extending discovery and identity support (Microsoft Entra Agent ID) to 60 types of local agents, including Claude Code, OpenAI Codex, and GitHub Copilot, and introducing 'Guardian Agents' that monitor and respond to risky agent behavior at machine speed.