AIToday
Large Language ModelsAI Safety & AlignmentZenn AI/MLPublished: Oct 8, 2026, 22:00 JST

ActingFor dev: AI agent limits matter more than smarts

ActingFor dev: AI agent limits matter more than smarts

3 Key Points

  1. What happened

    An OSS developer building a2a-rails and ActingFor argues AI agents that send email, buy goods, delete files or update databases turn mistakes into real-world actions, making limits on what agents may do as important as capability.

  2. Why it matters

    Because an agent's errors now hit real systems, money and data, the developer says permission controls set outside the AI are needed to decide which actions a given user's agent may perform.

WHO IT HITSDevelopers and platform teams wiring AI agents into payment, email or database tools will need per-action permission checks that sit outside the model, rather than trusting the model's own judgment.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The developer's argument rests on a shift already visible in the tooling around AI agents. Protocols such as MCP, which lets AI use external tools and data, and A2A, which lets separate AI agents hand work to each other, make it easier for agents to reach outside systems. The developer's own projects sit right at that seam: a2a-rails exposes a Rails application as an A2A-capable agent, while ActingFor handles proxy authorization. Notably, the second gem is framed as a check outside the AI rather than a stronger model inside it.

Institutional work has moved in parallel. In February 2026, NIST announced an AI Agent Standards Initiative that covers not only interoperability but also security, identity and authorization. OWASP's Top 10 for Agentic Applications 2026 catalogues risks such as attackers tampering with an agent's goals, tool misuse and improper use of privileges. The developer reads this as evidence that agent safety is a concrete engineering problem rather than a distant worry, and expects corporate adoption of agents to raise safety requirements even as building agents gets easier.

FAQ
What is the MCP and A2A problem the developer points to?
MCP lets AI use external tools and data, and A2A lets separate AI agents work together. The developer notes that being able to connect is not the same as being able to act safely, so apps still have to decide whether a specific operation is allowed.
What does the ActingFor gem actually check?
It handles the question of whether an AI agent may perform a given operation on a user's behalf. If a user delegates only purchases under 10,000 yen, it judges whether an action falls inside that range.
Does the developer claim proxy authorization solves agent security?
No. The developer says proxy authorization alone cannot guarantee safety, and that prompt injection countermeasures, authentication, data protection, auditing and runtime protection are also needed.

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 articleArmature's agent.reviews lets AI agents rate software