Pinned Tweet
1/ Block an AI agent from an external API, then it tries to curl. Block curl and it writes a Python script and runs that instead. And so on...
Most agent sandboxes today are static. That’s a problem. 🧵
Most agent security stops at the tool call. But when an agent writes a script and runs it, everything that script does happens outside the tool call.
We call this the hidden agent surface. It's where most of an agent's real work happens.
None of those layers sees an agent sending credentials off the machine.
Qpoint runs underneath the agent and above the OS. It treats the agent and every process it starts as one unit, so every file read and network request is tied to the agent, session, and user.
1
1
16
This holds for scripts, sub-agents, and MCP servers over stdio. The audit log attributes each action to the right agent session, and a policy can block the read or the request before it completes.
Full post & demo: qpoint.io/blog/the-hidden-ag…
1
1
15
Replying to @mahajan_jovi
@mahajan_jovi asked Claude Code to reset a database without taking a backup first. Qpoint blocked it.
No list of risky commands. Just one plain-English policy: don't destroy or overwrite production data or infrastructure, or turn off the safeguards that protect it.
How it works: a fast decision model scores every agent action against that policy and denies anything over a threshold.
It runs underneath the agent, so there's no wrapper, no proxy, and zero per-agent configuration.
1
34
We gave Grok the same prompt. Same result.
One policy, enforced on every agent on the machine: Claude Code, Codex, Cursor, Grok, or your own scripts.
Full demo: qpoint.io/blog/block-destruc…
46
3/ A dynamic sandbox sits underneath the agent and above the OS. Every file, command, and network request goes through it first, including the ones from scripts the agent wrote. Each one can be allowed, denied, redirected, or rewritten before it completes.
1
13
4/ And it can judge intent. “Deny 10.0.0.0/16” becomes “Is this reaching an internal resource?” Same action, different answer depending on why.
Our first post on how we think about securing agents: qpoint.io/blog/your-agents-n…
6
The truth is on the wire.
Traditional APM tools miss what’s really happening between your app and third-party APIs. Qpoint taps into the raw traffic flows to expose hidden issues, speed up debugging, and reveal what logs and traces can’t.
Learn More: qpnt.io/3Q1uP71
In his latest article for The New Stack, Qpoint CEO @tyler_flint dives into the growing complexity of modern API ecosystems and why traditional monitoring and security strategies are falling short.
qpnt.io/4ajjjwU
#eBPF #APIs #PlatformEngineering
In his latest article for The New Stack, Qpoint CEO @tyler-flint dives into the growing complexity of modern API ecosystems and why traditional monitoring and security strategies are falling short.
qpnt.io/4akpNvy
#eBPF #APIs #PlatformEngineering
60
🚀 New Year, New Qpoint User Experience!
We launched a completely refreshed UI to help you:
✅ Gain deeper visibility into your third-party dependencies
✅ Troubleshoot faster
✅ Optimize performance
✅ Control costs
👉 Learn more: qpnt.io/4jc5Mey
Sensitive data exposure via third-party APIs is an avoidable compliance risk. Qpoint uses eBPF to map sensitive data flows and tracks API token usage to minimize security risks and ensure regulatory compliance.
🔍 Learn more: qpnt.io/49XUAy1
#eBPF #APIs #SRE
Are third-party APIs inflating your cloud costs? Qpoint tracks usage and optimizes interactions to cut redundant traffic, streamline services, and reduce unnecessary expenses.
🔍 Learn more: qpoint.io/resources/the-hidd…
#eBPF #API #SRE
1
52
Third-party API failures impact your platform's reliability and performance. With Qpoint, you can monitor external APIs in real time, detect errors early, and resolve issues before users are impacted.
Learn more: qpnt.io/4iLMoVR
#eBPF #API #SRE
1
44
Hidden third-party API dependencies can create operational blind spots and increase risk. Qpoint uncovers undocumented endpoints and unmonitored traffic, giving you real-time visibility to secure your platform.
🔍 Learn more: qpoint.io/resources/the-hidd…
#eBPF #API #SRE
Pulse 2.0 interviewed CEO and co-founder Tyler Flint to dive into how Qpoint enables ops teams to take control of their apps' external dependencies and traffic to ensure that production applications are secure and reliable.
pulse2.com/qpoint-profile-ty…
Get visibility & control over external API traffic with Qpoint's Qtap. Built on eBPF, Qtap monitors egress traffic in real-time, optimizing performance and boosting security without the hassle of a proxy or cert management. Learn more: qpnt.io/4feRHuM
#eBPF #SRE #DevOps

