Access is a permission. Action is a decision.
Security needs a decision at the point where an agent's interpretation becomes a business consequence.
The gap appears after access is granted.
Agents choose their next step from prompts, retrieved material, tool results and messages from other agents. Their behaviour can change while their credentials stay valid.
An Action Firewall is an independent policy decision, made before the consequential operation runs.
A clear division of responsibility.
AgenticDome does not replace your identity provider or the systems behind your tools. Each part does its own job.
- The executor that carries out the action
- The trusted identity and purpose context
- The final arguments, as they will actually run
- What happens on failure
- The source of the evidence
Where the check sits, and what it can see.
The same policy applies wherever you place the check. The choice is about reach.
| Approach | What it decides | What it does not decide |
|---|---|---|
| Identity and access controls | Who may call, and what they may access. | Whether this specific action, with these final arguments, should run. |
| Policy services and network observation | Whether a rule matches, or what traffic occurred. | A matching rule or observed connection alone does not place an enforcement check at the final executor or establish a business outcome. |
| Action Firewall at the gateway | Each request to MCP servers, APIs, GraphQL and A2A, against one policy. | Actions that happen inside your application. |
| Action Firewall in the SDK | Actions inside the agent application, with richer context. | Calls that bypass the application. Add the gateway and Runtime Grid for those. |
You cannot govern what you cannot see.
Discovery finds agents, MCP servers and models, shows how each was found, and separates what is configured from what is actually used. Then you choose what to protect, connect it, and verify a real action.
See Discovery on the platform page- 1Discover what exists, what is used, who called it
- 2Connect protection on the execution path
- 3Verify with a real action and read the evidence
- 4Monitor the changes that matter
What we claim, and what we do not.
We would rather you know the limits before you buy.
- AgenticDome returns decisions for paths connected through supported integrations.
- It can help block denied operations when the receiving application or gateway enforces the decision.
- That installing a package protects every path.
- That all prompt injection is preventable.
- That a valid identity makes an action appropriate.
- That the local demo certifies a production deployment.
- That an allow decision proves the business transaction completed. Missing evidence stays missing.
- Agree the workflow.
- Test allowed and denied actions.
- Test what happens when the service is unavailable.
- Inspect the evidence.
See the decision before the action.
Start with one agent and one tool.