MoEngage has integrated AI agents into its customer engagement platform by using the Model Context Protocol (MCP) and Amazon Bedrock AgentCore to expose existing APIs as agent-callable tools. By treating its platform as an architecture of isolated sessions and standardized tool schemas, the company enabled teams to automate workflows and decision-making within a single conversation.
Cohere has unveiled Video Intelligence within its Compass platform, allowing AI systems to perform granular, timestamped searches across video libraries. It processes both audio transcripts and on-screen visual information to retrieve precise moments that answer specific user queries.
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.
AWS has published a guide on creating an event-driven architecture to automatically sync Model Context Protocol (MCP) tool schemas with the AWS Agent Registry. Using AWS CloudTrail, EventBridge, and Lambda, this pipeline detects runtime changes and updates the registry whenever an MCP server's tool schema evolves.
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.
AWS published a walkthrough for the Adaptive Agentic Intelligence Framework (AAIF), built on Strands Agents, which routes simple requests to small local models (via Ollama) and only sends complex requests to cloud models through Amazon Bedrock. A lightweight 1B-parameter model (llama3.2:1b) acts as an orchestrator deciding where each request should go, with an example IoT monitoring agent that uses local telemetry retrieval, local vision analysis, and cloud-based expert insights. AWS states that in the hybrid setup, roughly 80 percent of traffic can be handled locally without hitting a paid API, and the architecture can run fully on edge hardware (e.g. Raspberry Pi with 8GB memory), fully in the cloud, or in a hybrid mode.
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.
Eon, a data protection ISV running on AWS, replaced per-tool credentials and local MCP servers with a single Amazon Bedrock AgentCore MCP Gateway. The gateway uses Cedar-based policies to enforce least-privilege access for both human engineers and an autonomous SRE agent running Claude on Amazon Bedrock, routing calls to MCP servers hosted on AgentCore Runtimes across multiple AWS accounts. Developer onboarding time dropped from about two days to about two minutes after rolling the system out to 100+ developers and roughly 10,000 sessions.
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.
Google Cloud published a reference architecture for building AI agents that coordinate long-running, GPU-heavy scientific tasks like protein folding and compound screening, which break standard single-LLM-agent setups due to timeouts and context overflow. The design separates a cognitive orchestrator (Gemini on Agent Runtime) from a GPU execution layer (NVIDIA NIMs like ESMFold and GenMol on GKE) and wraps both in an enterprise governance plane with agent identity, a gateway, a registry and Model Armor. It also lays out best practices such as passing bulky data by reference instead of inline, streaming progress updates, and gating irreversible actions behind human approval.
Google has announced support for DPoP (Demonstrating Proof-of-Possession, RFC 9449) in its OAuth platform, cryptographically binding refresh tokens to a client-generated key pair so stolen tokens cannot be replayed by attackers. The protection applies only to long-lived refresh tokens, while short-lived access tokens remain standard Bearer tokens to avoid added cryptographic overhead on high-throughput API calls. Google also highlights DPoP's relevance for securing multi-agent and Model Context Protocol (MCP) architectures, recommending Google Cloud Secure Token Service for token delegation chains between agents.
AWS published a governance framework called Trust in Depth, designed to let AI agents operate with more autonomy while staying within enforceable limits. It combines scoping agent permissions before deployment, giving each agent a verifiable identity, enforcing boundaries at runtime via policy gateways, and observing agent behavior afterward. The framework leans on automated reasoning (mathematical proof) for rules that can be precisely defined, and human judgment for ambiguous cases, using AWS tools like Bedrock AgentCore, Guardrails, Kiro, Strands, Agent Registry and CloudWatch Omni.