Backed by $12 million in seed funding, Metano helps enterprises secure AI agents wherever they operate, including endpoints, cloud and SaaS.
Metano Product Team
Maya Chen is an AppSec engineer who also creates and ships agent skills. One afternoon, a teardown of a poisoned skill in a security Slack prompts a more practical question than how the exploit works: what can her agents see, and what could they leak? She wants to map both the access footprint - the accounts, folders, and endpoints each agent can reach - and the blast perimeter - the systems, APIs, and secrets within that reach. But she has no inventory to answer either question.
She can’t answer it. Nor can most security teams. Maya is pretty convinced there’s real exposure, but suspicion alone won’t get her CISO to commit any budget. She needs proof, and she doesn’t have time for a sales call, a full-blown install, or a procurement cycle just to get it.
Coding agents, MCP servers and skills get installed in seconds, typically by individual devs. Each grant looks perfectly reasonable in isolation: shell access for a project, a filesystem server for convenience, a database role for a demo. The problem is that the scope is often far wider than intended and it all compounds. A skill that can read key files plus a server that can reach the internet is an exfiltration path that you won’t see in any one config file.
Your current stack wasn’t built to catch this. EDR, CASB and the network gateways each look at their own layer. None of them were built to see agent behavior at runtime (e.g. which skill the agent loaded, which MCP server it called, what it was permitted to do without approval).
There’s also no central view of the agent registry. No one has a list of which agents, servers and skills are running on which laptops and what each one can touch. That’s your blast radius and it’s completely invisible at the moment.
Rule of thumb: if anyone on your team runs a coding agent with skills or MCP servers installed, you have a blast radius worth measuring.
| What you get | Why it matters |
|---|---|
| Blast radius map | A sunburst view of every agent, MCP server, and skill, and everything each one can reach. |
| AIThreatPaths | The exact routes a malicious skill could take, such as SSH key to the open internet. |
| Plain-language findings | Every risk in one sentence, sorted worst-first: what can happen, and to what. |
| Guided fix and rescan | Proof that risk actually went down, not just a list of what is wrong. |
| Proof on a clean scan | A test skill, a coverage meter, and a “Verified clean by Metano” report. |
| Drift alerts | A heads-up when a newly installed skill or MCP server creates fresh exposure. |
| Evaluation report | Executive-ready evidence to forward to your manager or CISO, with a direct path to a POC. |
The scan inventories the agents on your laptop, the MCP servers they connect to, and the skills installed in them, broken down into six component types:
| Component | What the scan shows |
|---|---|
| Models | Which models your agents are set up to call. |
| Skills | Every installed skill, including community skills, and what each can read or send. |
| Plugins | Extensions added to your agents and the access they bring. |
| Tools | The tools agents can use, such as shell or filesystem access, and whether they need approval. |
| Packages | The packages your skills and servers depend on. |
| MCP servers | Every server each agent connects to, how widely it is scoped, and whether it requires authentication. |
You see it all at once on a sunburst map running from each agent out to everything it can reach. AIThreatPaths then traces how one permission chains into another, for example from a local SSH key to an external destination.
Every finding is a single complete sentence stating what can happen and to what. No raw logs. No JSON. No severity codes to decipher.
| Typical scanner output | What Metano tells you |
|---|---|
| Reads, reaches, sends. No approval. | Data can leave this laptop without anyone reviewing it. |
| Shell allowed for every project, no approval | The agent can run any shell command without asking. |
| Skill reads key files and reaches the internet | A skill can read your SSH key and send it to the internet. |
| Read-write role on production customer DB | The agent can change records in the production customer database. |
| Filesystem MCP scoped to the whole home folder | Claude Code’s filesystem server can read your entire home folder. |
Each finding is already a risk statement so you can just pass it on to your manager or CISO as is.
The scan runs once and nothing stays on disk. It needs a single outbound connection to edge.metano.ai:443.
The findings are ordered by blast radius so the one that has the biggest exposure is at the top. The fix is in plain language (what to change, not just which setting is wrong). You apply it, rescan and the rescan confirms your exposure has actually gone down, with a fix meter showing you progress (“1 of 3 fixed”).
Would you prefer to go through the findings before making any changes? Select “Not yet” to view all the findings, worst first. Either way you’ll end up with a full evaluation report for your manager or CISO.
See everything your AI agents can reach from a single command in minutes with absolutely nothing left on disk and walk away with proof that your CISO will act.
For the engineer that’s an answer in an hour rather than a quarter. For the security lead that’s evidence rather than opinion. For the organization that’s a very low risk first step before you go any further.
Metano Eval is deliberately narrow. It shows what one laptop exposes at the moment you run it. Two things sit outside its scope:
We state these limits upfront so your report is honest about what it proves. One laptop is usually enough to show the risk is real; the POC shows how far it extends.
Product-led security means ditching the high friction of the enterprise model. It’s minimal steps, plain language findings, proof from clean scans, one action per state and a blast radius that’s visible in minutes. That’s the bridge from a single laptop trial to an organization-wide rollout.
When an AppSec engineer sees her AI blast radius without having had a sales call, trust is instant. That trust then turns the evaluator into the internal champion who takes that report and walks it into the CISO’s office.
Start your 30-day Metano evaluation: one work email, one command, your full AI blast radius.

Metano Product Team
The team that builds Metano’s runtime defense for AI agents.
The latest news, technologies, and resources from our team.
Backed by $12 million in seed funding, Metano helps enterprises secure AI agents wherever they operate, including endpoints, cloud and SaaS.
Metano Product Team
A compromised AI tool could slip an ordinary-looking link into Jan’s chat. One click handed an attacker page the app’s internal powers, and it ran any program on the user’s machine, no password, no second prompt.
Parth Shukla
A prompt-injected agent in Amazon’s Kiro Crew could disable its own sandbox by editing a single config file. The file was writable from inside the sandbox, and a feature that skipped the security gate removed the last thing that would have questioned it.
Harsh Akshit
Since 21 October, computers infected with Mini Shai-Hulud have uploaded stolen secrets to 990 public GitHub repositories; the newest was created just 12 minutes before we counted. They upload using a stolen GitHub token that infected computers pass among themselves.
Japneet Singh
Anthropic’s inference hooks let a security server allow or deny every Claude Enterprise prompt and tool call before the model runs. Metano is now that server. It works on any device, with nothing installed.
Metano Product Team
Exposed LiteLLM gateways that still use the sample admin key will hand out API keys to anyone who asks. Each key is unique, so we could follow it to see who used it next.
Neelima Rustagi and Sonali Tyagi
Occasional updates, new content, and insights. No spam; unsubscribe anytime.