Recent experiments at Block showed that a group of new hires could, on their first day, receive an unfamiliar codebase, access AI coding agents, and deliver customer solutions within a day and a half. The success of that trial, combined with the open‑source agent Goose, signals a concrete move toward treating AI agents as first‑class participants in the software development lifecycle. Engineers across AI, cloud, DevOps, and security domains need to understand the new protocols, operational patterns, and governance questions that accompany this change.
Standardizing Agent Integration with MCP and A2A
Angie Jones, VP of the Agentic AI Foundation, highlighted two emerging specifications that aim to stabilize agent interactions:
- Model Context Protocol (MCP) – a contract for connecting agents to applications, providing a predictable interface for passing context and receiving responses.
- Agent2Agent (A2A) – a coordination standard that defines how multiple agents can collaborate on a shared task.
When multiple companies adopt these specifications, developers gain reusable interfaces that survive rapid model releases. The MCP Associate certification now offers a way to demonstrate competence with this contract, though certification is optional.
Designing the Agent Decision Loop
Building a reliable agent requires explicit control over its execution loop: choose an action, examine the result, and decide the next step. Practitioners must decide where to constrain this loop and what data the agent may access. In Block’s rollout, a small engineering team hardened the development environment to make it agent‑friendly, allowing agents to point at a repository and inherit lessons from prior prompting sessions without requiring each user to stay up‑to‑date.
Operational Practices: Issue‑First Workflow and Automated Triage
Goose’s maintainers shifted to an issue‑first process. Contributors first discuss the problem and design before any code is generated, ensuring that agents produce patches aligned with project intent. Agents are also employed to triage issues, run security scans, and perform initial code reviews, feeding results into the pull‑request queue. This approach preserves human oversight while leveraging agent speed.
Security and Governance Considerations
The foundation’s working groups are already tackling identity, reliability, security, and governance for agents in production. Key considerations include:
- Defining the scope of data an agent can read or write, especially when customer data is involved.
- Ensuring that agent‑generated changes still pass human review before merging.
- Applying existing security scanning tools to agent‑produced code to catch regressions early.
These practices help mitigate the risk of agents unintentionally exposing or corrupting data.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
Teams should evaluate whether their current CI/CD pipelines can accommodate MCP‑compliant agents and consider adopting an issue‑first workflow to keep human intent in the loop. Start by sandboxing agent access to repositories and data, and use the MCP Associate certification as a benchmark for internal skill development. Monitoring the evolution of MCP and A2A standards will be essential as the ecosystem matures.
