trending

How are you actually securing your AI agents right now?

We're launching AxioRank tomorrow (the security gateway for AI agents), and before

we do I'm curious how this community is handling it today.

  • If you have agents calling tools, APIs, or databases: are they on static keys or

    short-lived identity?
    Do you enforce a policy on what they can do, or mostly log it

    after the fact?
    And could you prove to an auditor what an agent was allowed to do?

    Genuinely want to hear what's working and what isn't.

Watching your AI agents isn't the same as securing them

Most AI security tools inspect prompts and flag bad content. Useful, but the agent

still authenticates with a static key and a log you have to trust.

Our take: security has to be enforced at the chokepoint, before the action reaches

your systems, with an identity per agent and an audit you can verify.
We're launching AxioRank tomorrow on this thesis. Curious whether you agree or push back.

We built an open standard for governing AI agent actions (AGS-1)

While building AxioRank we kept hitting the same gap: no agreed way to prove an AI agent's action stayed inside policy.

So we wrote one, AGS-1, with a verifier anyone can run offline. Launch is tomorrow. Happy to answer anything about the spec or why we went open.

AxioRank - The security gateway for AI agents | identity, policy, audit

Most AI security tools just watch. AxioRank enforces. It sits between your AI agents and the tools, APIs, and data they touch, giving every action three things competitors don't combine: short-lived identity instead of static keys, default-deny policy you control, and a signed audit trail you can verify offline (no trust in us required). Open AGS-1 spec, drop-in gateway, works with any agent or MCP server.