logoalt Hacker News

qnleighyesterday at 5:33 PM1 replyview on HN

It seems like the most unreasonable thing happening here is Railway's backup model and lack of scoped tokens. On the agent side of things, how would one prevent this, short of manually approving all terminal commands? I still do this, but most people who use agents would probably consider this arcane.

(Let's suppose the agent did need an API token to e.g. read data).


Replies

Vespasianyesterday at 6:47 PM

Wrapper around the function call. Don't give it the token itself but a limited set of fixed functions to create domains (their use case according to the post).

Additionally give it a similar restricted way to "delete" domains while actually hiding them from you. If you are very paranoid throw in rate limits and/or further validation. Hard limits.

Yes this requires more code and consideration but well that's what the tools can be fully trusted with.