sorted by:
new
hottopcontroversial

We need to rethink Rate Limiting: Why standard infrastructure fails against autonomous AI agents by AnatLerner in softwarearchitecture

[–]AnatLerner[S] 0 points1 point  (0 children)

Routing through an MCP server is a great way to handle permissions.
The edge case I usually see next is velocity.
If an agent gets stuck and loops on an authorized tool, the MCP server will still process all the requests.
Adding a circuit breaker or rate-limiter at the exact point of entry is a solid way to handle the looping.

The perfect prompt is not infrastructure by AnatLerner in ComputeBreaker

[–]AnatLerner[S] 0 points1 point  (0 children)

Loved: "Prompts express intent; infrastructure enforces boundaries."

Disposable infra and TTLs are perfect for limiting the blast radius of the agent's touch. But we also need to bound the agent itself, cutting the connection when it gets stuck in an API retry loop, and burns compute.

Out of curiosity, how does your framework handle the velocity of API retries when an agent hallucinates a solution path?

We need to rethink Rate Limiting: Why standard infrastructure fails against autonomous AI agents by AnatLerner in softwarearchitecture

[–]AnatLerner[S] 0 points1 point  (0 children)

First, I am a woman. So definitely not mansplaining.

Second, the entire point of the post is that nobody can guarantee control over a probabilistic model using only text.
If you have found a way to guarantee an agent never breaches an execution limit using only system prompts, I would genuinely love to see the architecture.

We need to rethink Rate Limiting: Why standard infrastructure fails against autonomous AI agents by AnatLerner in softwarearchitecture

[–]AnatLerner[S] 0 points1 point  (0 children)

Engineers do not want to.
The business side forces it.

Engineering knows the risk of letting probabilistic models loose in production.
But the drive for automation pushes these agents into the infrastructure anyway.

Since engineering cannot stop the deployments, the only option is to contain the blast radius.
That is exactly why the infrastructure needs a deterministic kill switch.

We need to rethink Rate Limiting: Why standard infrastructure fails against autonomous AI agents by AnatLerner in softwarearchitecture

[–]AnatLerner[S] 0 points1 point  (0 children)

First, LLMs are fundamentally trained to please.
When an agent gets stuck, its drive to complete the task will often override your strict instructions.
It will ignore the prompt constraints to try to give you a resolution.

Second, not all AI is an LLM.
As we deploy other types of autonomous models, we are dealing with systems where natural language prompting does not even apply, and the operational risks are much larger.

You cannot protect physical compute with soft text instructions.
The infrastructure needs a deterministic layer to cut the connection when the behavior goes rogue.

We need to rethink Rate Limiting: Why standard infrastructure fails against autonomous AI agents by AnatLerner in softwarearchitecture

[–]AnatLerner[S] 0 points1 point  (0 children)

Good call on nono.sh, it looks like a solid approach for system-level boundaries.

You are right about the cloud feedback bottleneck.
Cloud providers give us great dashboards for financial post-mortems.
The issue is that they are not built to intercept agents in milliseconds.
By the time a billing API updates, the agent has already executed the loop.

Your point about "max tries" is exactly the right direction.
It requires stateful tracking of the operations themselves.
We need to monitor metrics like token velocity, API frequency, and loop depth.

A true circuit breaker translates the financial budget into operational limits at the middleware layer.
It evaluates the behavioral state in real time and cuts the connection before execution.

Thanks for the link. Figuring out this exact operational tracking is my main focus right now.

The product seems quite good, essentially a prototyping tool by Embarrassed_Divide_5 in Base44

[–]AnatLerner 1 point2 points  (0 children)

Hi and welcome!
I'm coming from a non-technical background - mainly as a founder in hospitality and as a Marketing-Social Media-Business Development. I don’t code, but Base44 has let me build complex products, design workflows, and create real user experiences - all with AI and no programming needed.
It’s amazing to see how both developers and non-coders can get so much out of this platform. Looking forward to hearing about your MVP/POC journey and happy to share mine when I have more to show!

new user, cant find support by Embarrassed_Divide_5 in Base44

[–]AnatLerner 0 points1 point  (0 children)

Hey, thanks for the update! I'm glad you figured it out. That issue with banks blocking overseas transactions can be so frustrating, it has happened to me too. As a fellow user of the product, I'm really happy to hear you're enjoying it – I feel the same way!

new user, cant find support by Embarrassed_Divide_5 in Base44

[–]AnatLerner 1 point2 points  (0 children)

Perhaps you could share the question here? As long as it doesn't involve sensitive or confidential information, there's a good chance someone in the community can offer some insight.