AIToday
Large Language ModelsHacker NewsPublished: Jul 26, 2026, 13:01 JST

Axtary: Content Authorization System for AI Agents

Send on LINE
Axtary: Content Authorization System for AI Agents

3 Key Points

  1. What happened

    Axtary, a content authorization platform, has launched to control what AI agents can do by checking exact diffs, messages, queries, or tool payloads before execution. Routine actions follow policy automatically; higher-risk actions require human approval of the specific payload.

  2. Why it matters

    As AI agents operate in sensitive domains—code changes, infrastructure, data access, Slack messages, tickets—keeping their authority limited and auditable is critical. If an agent is mistaken or compromised, Axtary's exact-payload binding means it can only execute what was explicitly approved, not a broader permission. Every attempt is recorded in a ledger.

  3. What to watch

    Axtary is available at v0.5.0 on npm and supports runtimes from Anthropic, OpenAI, and Cursor, plus native connectors for GitHub, Slack, Linear, Jira, Sentry, PostgreSQL, AWS, Google Cloud, and Google Drive. Microsoft, Okta, and Auth0 connectors are coming soon; enforcement runs locally while a hosted control plane coordinates policy and approvals.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

Axtary addresses a growing concern in AI agent deployment: the tension between capability and control. As agents take on sensitive tasks—committing code, updating infrastructure, posting to company channels, querying databases—the permission model becomes critical. Traditional tool-based access control grants broad permissions (e.g., "use Slack" or "write to GitHub") with limited visibility into what each invocation actually does. Axtary inverts this by enforcing authorization at the payload level: not "can the agent use GitHub?", but "is this exact pull request diff what the human reviewed and approved?"

The platform's architecture separates concerns deliberately. Local enforcement and credential storage mean sensitive operations never transit a central server in the approval path; the hosted control plane only orchestrates policy, review workflows, and audit trails. This design reduces the blast radius if the hosted service is compromised—an attacker cannot directly trigger privileged actions without local verification. Axtary's support for both MCP (Model Context Protocol) servers and native connectors to mainstream platforms (GitHub, Slack, AWS, Google Cloud) suggests it aims to fit into existing AI agent runtimes without requiring architectural rewrites.

FAQ
How does Axtary prevent an agent from misusing an approved action?
Axtary binds human approval to the normalized action and payload hash. If the payload changes after approval, adapter-side verification rejects the mismatch before the provider is called, and both the approved and presented hashes are recorded in the ledger.
What platforms and tools does Axtary support?
Axtary supports runtimes from Anthropic, OpenAI, and Cursor, and native connectors for GitHub, Slack, Linear, Jira, Sentry, PostgreSQL, AWS, Google Cloud, and Google Drive. Microsoft, Okta, and Auth0 connectors are coming soon.
Where do credentials and enforcement run?
Enforcement and credentials remain local in SDKs and a local proxy. The hosted control plane coordinates team policy, approvals, and audit exports without entering the action data path.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAlphabet purchase commitments top $811 billion for AI infrastructure