Trusted2Act

Linus Håkansson asked his desktop agent to help with a busy week, and it deleted a bunch of his calendar invitations. It was allowed to. He'd connected it to Google Calendar over MCP and handed it his own rights to create, update and delete, so the agent acted as Linus with everything Linus could do.

ㅤ

In the first episode of Trusted2Act, Tim Tyler and Linus work through the six principles of the Agent Accountability Framework: identity, sponsor, role, authority, oversight and recourse. Linus speaks from both sides of the house. He argues against pulling the handbrakes on agents, then spends the conversation on what security and identity teams need answered before an agent acts.

ㅤ

The boundary he draws is a default. A new agent gets its own identity, separate from the human it works for, and starts with no authority until a sponsor or owner grants it. Destructive actions go back to a human first.

ㅤ

👤 Guest Bio

Linus Håkansson is Chief Product and Technology Officer at Gravitee, which presents Trusted2Act. He joined Gravitee in 2021 and has served as VP of Product, Field CTO and Chief Product Officer. Before that he held architect roles at cloud and integration technology companies. He studied engineering at Lund University and is based in London. On this show he speaks for both sides of the house: the builder who wants agents in production and the person who has to answer for what they do.

ㅤ

📌 What We Cover

• Why giving agents the same identity and credentials as humans is one of the most common mistakes Linus sees, and why every agent belongs in a registry recording who built it and who owns it.
• The corridor test: an agent should be able to answer "who are you?" with short-lived, machine-generated credentials, not a hard-coded API key.
• The sponsor, the human who answers for an agent's actions, its costs and whether it delivers, and why accountability runs in two layers.
• Putting budget into an agent's role, and the company that found daily weather checks on an expensive model had turned into a big financial issue.
• Authority across the three things an agent talks to: models, tools and other agents.
• Guardian agents, approvals granted "under this condition, for this period of time," and revoking the lanyard.
• Why twelve-month penetration tests and compliance cycles give way to always-on red teaming once agents try every combination of a URL.

ㅤ

🔗 Resources Mentioned

• Agent Accountability Framework
• Model Context Protocol (MCP)
• Claude Desktop, Google Calendar, ChatGPT
• LangChain, Kubernetes, Workday, ServiceNow
• Guardian agents
• SOC 2 and ISO certification

ㅤ

Trusted2Act is presented by Gravitee.

AI agents are already moving money and touching customer data at machine speed, and CEOs want more of them. But who owns those agents, who sets the rules, and who has a plan for when one goes wrong?

ㅤ

Trusted2Act is a weekly show about the tension every enterprise now faces: ship fast enough to stay ahead, govern well enough to stay accountable. Host Tim Tyler sits down with the platform leaders, security architects, and AI champions running agents in production.

ㅤ

First episode Wednesday, September 9. Subscribe wherever you listen, and visit trusted2act.com.