
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.
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.
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.
Summaries like this, every morning.
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.
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 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.
SORACOM's Makoto Yazaki trained Wisora on its own service and documentation pages, then asked how to register…

A solo entrant finished 67th of 6,299 teams in Kaggle's RSNA Knee Abnormality Detection contest, scoring a Pri…

The blogger ordered a used Fujitsu LIFEBOOK U938 for 15,800円 but received a U939 with a Core i5-8365U, 8GB RAM…

A Zenn post lays out five steps for rewriting AI-generated technical drafts, starting by pasting terminal logs…

From late October, the developer sent bounded implementation and research tasks through OpenCode's HTTP API to…

Shane Melaugh analyzed about 1,400 Claude Code sessions with Gemini 4 Argon and found the share of sentences s…
