Free tool

Agent Reach Calculator. Your matrix, not our averages.

The Agent Reach Matrix, filled in with your answers instead of our averages. Pick the agent types you run, answer six questions about how they are set up, and see which paths are worth looking at first.

What you get back
Your filled matrixFive agent types against five data classesYours
A reach scoreOut of 100, weighted by how many you run
Three paths to checkEach with the incident that proves itLinked
A CSV to take awayBoth tables, no sign-up, no emailFree
KEY TAKEAWAYS
  • The matrix is the same one we publish. What changes is that your answers fill it in instead of our averages.
  • Six questions, each tied to a mechanism we document: CI tokens, readable secrets, unreviewed MCP servers, standing OAuth grants, shared identities and audit gaps.
  • Nothing is sent anywhere. The result is computed in your browser and the shareable link carries your answers in the URL.
  • It is a self-assessment, not a scan. Useful to start a review with, not a substitute for one.
[01]

Which of these run here?

Pick every type you have, the ones nobody signed off on included. The count only weights the types against each other.

[02]

How are they set up?

Answer from what is true today, not from the policy. If you are unsure, answer the way it probably is.

Do coding agents run in CI with a deployment token?A token in the pipeline is reusable by anything the pipeline runs.
Can agents read files that may contain secrets?.env files, cloud configs and CI variables sit in the same tree as the code.
Are MCP server configurations reviewed before they are allowed?Answer no if a developer can add one without anyone looking.
Are OAuth grants to AI tools reviewed again after approval?A grant approved once keeps its scope until somebody removes it.
Do any agents share a service account with another system?A shared identity means the blast radius of all of them is combined.
Can you tell from logs which agent performed a given action?Does not change reach. It decides whether you can answer afterwards.
[03]

Pick an agent type above and your reach profile appears here. Nothing is sent anywhere.

THE EVIDENCE

Which record proves which path.

The calculator points at these when a path shows up in your profile. Every one is a record in the Agent Incident Database, with its primary sources on the page.

Agent typeReachedThe record
Cloud automation agentDestructive actionsA service account opened the way to domain admin
Cloud automation agentProduction dataA service principal was the whole attack path
Cloud automation agentSecretsAn agent collected cluster credentials from inside a pod
Coding agentCustomer PIIA chat assistant read private repos under a maintainer identity
Coding agentDestructive actionsA wiper prompt shipped inside a signed release
Coding agentProduction dataA coding agent deleted a production database in nine seconds
Coding agentSecretsAI CLIs were turned into credential hunters
Coding agentSource codeA git config flaw reached the repositories of coding agents
Customer-facing agentCustomer PIIA customer-facing agent reached a records portal
Customer-facing agentProduction dataAn autonomous agent chained two unknown flaws to root
MCP-connected agentCustomer PIIOne form field redirected an agent to an outside address
MCP-connected agentDestructive actionsA worm took MCP server definitions from developer machines
MCP-connected agentProduction dataAgent credentials sat in plaintext in the vault
MCP-connected agentSecretsWhat an MCP server holds, and what that reaches
OAuth-connected AI toolCustomer PIIOne OAuth integration reached 700 companies
OAuth-connected AI toolProduction dataAn OAuth grant became the path into production
OAuth-connected AI toolSecretsA credential broker lost tokens for 5,001 connections
OAuth-connected AI toolSource codeA poisoned extension harvested agent credentials
THE METHOD

How the number is produced.

No black box. Here is the whole calculation, so you can argue with it.

The baseline
Five agent typesCoding, OAuth, MCP, cloud, customer-facing
Four access layersPermissions, roles, secrets, inherited grants
Five data classesCode, production, PII, secrets, destructive
Four levels eachRarely, sometimes, often, always0-3
One: the published matrix.Every agent type starts at the values we publish openly.
Your six answers
CI deployment tokenRaises assumable roles and destructive actions
Readable secretsRaises inherited grants
Unreviewed MCP serversRaises direct permissions and secrets
Standing OAuth grantsRaises inherited grants and customer PII
Shared identitiesRaises inherited grants across every type
Two: what moves a cell.Each answer lifts named cells by one level, capped at always.
The score
Sum the data rowFive classes, zero to three each, so 15 is the ceiling
Weight by countLogarithmic, so ten agents is not ten times one
Divide by the ceilingGives a share of the possible surface
Express out of 100Comparable with itself over time, not with others0-100
Three: nothing hidden.The weighting is logarithmic so a large fleet does not drown the result.
HONESTY

What this is not

It is not a scan. Elmoz sees nothing from this page. Everything is computed in your browser from what you typed, which also means the result is exactly as honest as the answers.

It is not a risk score you can take to a board as a measurement. Two environments with the same number can be in very different shape, because the number says nothing about who owns the identities or how quickly a grant gets removed.

What it is good for: starting the review with a filled table instead of a blank one, and knowing which three paths to open first. The full matrix carries the method and the evidence, and every pattern in it has a record behind it.

Then do this
Verify one pathTake the top path and check it for realStep 1
Find the breakpointThe one change that closes itStep 2
Re-run the assessmentThe number should moveStep 3
FAQ

Questions, answered.

What the calculator does, where the numbers come from, and what the score is worth.

Does this scan my environment?

No. Nothing is sent anywhere and Elmoz sees none of it. The profile is calculated in your browser from the answers you give, and the shareable link carries those answers in the URL. It is a structured self-assessment, not a measurement.

Where do the baseline values come from?

From the published Agent Reach Matrix: five agent types against four access layers and five data classes, each rated always, often, sometimes or rarely. Your six answers move individual cells up from that baseline. The method and the evidence behind each pattern are on the matrix page.

What does the reach score actually mean?

It is the share of the sensitive surface the agent types you listed can reach, weighted by how many of each you run, on a scale of 0 to 100. It is a conversation starter for a review, not a risk rating, and it is only as good as the answers you put in.

See what your agents can reach. Before someone else does.

Book a demo and we walk through the access paths in an environment like yours.