Liam McD (@LTM_yvr) header
Liam McD (@LTM_yvr) profile picture

Sales @1Password | 🏆 AE of The Year ‘25 | 🇬🇧🇨🇦 | New Father | Tec 50 Diver | Star Wars nerd | Gamer | SWFC🦉

Vancouver, British Columbia
Joined July 2026
Photo by Liam McD (@LTM_yvr)Photo by Liam McD (@LTM_yvr)Photo by Liam McD (@LTM_yvr)Photo by Liam McD (@LTM_yvr)Photo by Liam McD (@LTM_yvr)Photo by Liam McD (@LTM_yvr)Photo by Liam McD (@LTM_yvr)Photo by Liam McD (@LTM_yvr)Photo by Liam McD (@LTM_yvr)
1Password’s Developer Watchtower is a BIG deal: find and vault secrets on dev machines without breaking workflows. Then it get better, after vaulting you can work with your agents and give them access without sharing the secrets themselves.
Most security incidents don’t start with sophisticated hacks. They start with credentials that have too much access. Here are 5 practical steps every developer can take to secure their apps, tools, and AI agents. �
3
89
Using agents, or thinking about it but concerned about security? Give this a listen 👇🏻
New episode of Random but Memorable is live 🎙️ KC Li, senior director of product management, joins to talk about 1Password for Agents: how agents sign in for you without ever seeing your passwords. Watch now: youtube.com/watch?v=o9UDSh4t…
3
41
New episode of Random but Memorable is live 🎙️ KC Li, senior director of product management, joins to talk about 1Password for Agents: how agents sign in for you without ever seeing your passwords. Watch now: youtube.com/watch?v=o9UDSh4t…
4
3
28
85,268
Most security incidents don’t start with sophisticated hacks. They start with credentials that have too much access. Here are 5 practical steps every developer can take to secure their apps, tools, and AI agents. �
3
11
3
62
310,486
Your AI co-pilot runs with your credentials: same prod access, same push rights, and no separate identity. Here’s why that’s a real risk, and how to scope agent access without slowing your team down. 🧵 1/5
2
6
19
18,607
Liam McD retweeted
AI agents need access to your accounts. But how can you let them use your credentials without putting your security and privacy at risk? 1Password for Agents’ security model gives agents a secure, seamless way to request access and sign in, while making sure that you always stay in control of your information. 🔗Read more here: bit.ly/4sTrZDD
17
16
4
231
31,228
If an agent got hold of one of your secrets, ask yourself how far could it get in just 5 minutes.
Every day now seemingly brings another breach, and the postmortem almost always ends the same way. A credential was compromised, and it could reach far more than it should have. We spend enormous energy trying to prevent the breach. Prevention matters, but I think we ask the wrong question afterward. The question is not only how did they get in. It is why did one stolen credential open so much. Breaches are inevitable. Blast radius is a choice. Every standing credential in your environment is pre-authorized damage. The API key on a hard drive that never expires. The token sitting in a config file. The agent running with persistent access to systems it touches once a month. When one of them leaks, and one of them will, the damage was decided by choices made months earlier. So what can we do? Secure exposed credentials. Give every identity, human or agent, only the access it needs, only for as long as it needs it. Know where every credential lives, who owns it, and how to revoke it. Agents make this urgent. Handing an agent your credentials is not automation. It is delegation without accountability. You cannot shrink a blast radius you cannot see. Start by looking. How much standing access do you have? Most teams I speak with cannot answer that today. That gap is the risk. Breaches are inevitable. What happens next is up to us.
1
2
111
Every day now seemingly brings another breach, and the postmortem almost always ends the same way. A credential was compromised, and it could reach far more than it should have. We spend enormous energy trying to prevent the breach. Prevention matters, but I think we ask the wrong question afterward. The question is not only how did they get in. It is why did one stolen credential open so much. Breaches are inevitable. Blast radius is a choice. Every standing credential in your environment is pre-authorized damage. The API key on a hard drive that never expires. The token sitting in a config file. The agent running with persistent access to systems it touches once a month. When one of them leaks, and one of them will, the damage was decided by choices made months earlier. So what can we do? Secure exposed credentials. Give every identity, human or agent, only the access it needs, only for as long as it needs it. Know where every credential lives, who owns it, and how to revoke it. Agents make this urgent. Handing an agent your credentials is not automation. It is delegation without accountability. You cannot shrink a blast radius you cannot see. Start by looking. How much standing access do you have? Most teams I speak with cannot answer that today. That gap is the risk. Breaches are inevitable. What happens next is up to us.
4
5
2
11
78,497
Engineers should not be handing their over-privileged (standing) access to their agents. Allowing engineers to work with agents requires agent access to be JIT scoped to the task and removed after completion.
How much standing access is attached to your people and AI agents? 1Password Privileged Access provides just-in-time, just-enough access for cloud environments. Access is granted only when requested, scoped to the exact task, and removed automatically when the work is complete. See how just-in-time access can secure cloud and agentic AI workflows. 🔗 Register for the webinar here: bit.ly/4A7aqCu
1
30
How much standing access is attached to your people and AI agents? 1Password Privileged Access provides just-in-time, just-enough access for cloud environments. Access is granted only when requested, scoped to the exact task, and removed automatically when the work is complete. See how just-in-time access can secure cloud and agentic AI workflows. 🔗 Register for the webinar here: bit.ly/4A7aqCu
1
5
1
8
50,964
Builders came from across the Universe to Barrio in Ghirardelli Square for @1Password Agents After Dark with @databricks . 📷 Great views, great people and great conversations! #GitHubUniverse #AgentsAfterDark
2
4
2
14
9,363
Every day we hear about another attack on an AI platform. Credentials and API keys keep coming up. Someone gets your API key. Now they can use it to access your accounts or run up your AI bill. Here are 3 things you can do today. 🧵
2
7
38
61,084
Replying to @Replit
@Replit's CEO @amasad makes a great point. The more we ask coding agents to do, the riskier it gets to let them use our credentials... Better to give your agent its own identity and temporary access to what it needs for the task. Keep your credentials to yourself!!
AI agents running on employee endpoints are becoming a systemic security risk for enterprises & governments. Some are responding by restricting tools like Claude Code, as Goldman Sachs reportedly has. In this security advisory, we outline the risks and recommend a path forward.
3
4
433
Liam McD retweeted
It's been a rough few weeks for security. I pulled together a guide of the highest-impact actions you can take today:
96
252
86
1,543
342,172
Lots of things 1Password can help with: the password manager and passkey piece (obviously), and also - identifying and vaulting dev secrets on endpoints(SSH keys, .env files) - identifying shadow AI usage in browser and endpoint - ensuring secrets don’t get passed onto agents - eliminating standing access to dev, production, cloud etc for humans and agents - ensuring access is JIT, narrowly scoped to the task and cut off after use Doing it all in an easy to use, non disruptive way for engineers and end users.
It's been a rough few weeks for security. I pulled together a guide of the highest-impact actions you can take today:
54
Giving your agent access has never been easier 🔐 3 simple steps with @1Password + @Muse : - Your agent requests access. - You approve in 1Password. - 1Password fills the login. Your agent never sees your password. You stay in control. Your agent gets to work.
1
2
10
691
Liam McD retweeted
1Password Privileged Access is named as an Honorable Mention in the 2026 @Gartner_inc® Magic Quadrant™ for Privileged Access Management. As cloud environments become more dynamic, standing access creates risk for every identity, from employees and contractors to service accounts and AI agents. 1Password Privileged Access helps organizations move from permanent permissions to just-in-time, just-enough access for people, workloads, and AI agents. Read more about the recognition and how 1Password is helping organizations secure access at runtime: bit.ly/4szHdh6
3
4
30
7,013
How quickly could your team find and rotate every copy of an exposed credential without breaking production? Great blog from 1Password on actions to take and what to look out for.
25
🙌🙌🙌 now go forth securely and book that hard to find restaurant reservation, that flight, hotel m, or what ever else you can think of!
Replying to @Muse
@Muse, from @Meta, can now sign in without seeing your passwords. With 1Password for Muse, you can approve the login Muse needs and let 1Password handle the sign-in. Muse stays on task, and your passwords stay protected. Now available on Android and web, with iOS coming soon. 🔐
1
16