CLIs live in the same namespace as the agent, so any secrets the CLI needs access to, the agent can also exfiltrate. And access control is lightly gated by the agent's tool call policy.
For an enterprise-level deployment, it becomes quickly desirable to have a centralized MCP backbone, on which each MCP is attached to. A place you can attach policies to, log activity, and reason about access control.
Maybe. This phenomenon of security holes being found closely to each other was also common before LLMs. People attention gets directed to a place and typically more issues are getting found.
My assumption was that a tool like this will make it easier to keep the README.md in sync while the project evolves. Think of a `--help` section. That assumption holds true to me.
One thing I miss the most when writing Markdown is this formula experience you get in Excel. Jot something down, get the result. Then link it to another block.
There are tools like Jupyter notebooks that have all the functionalities, but their file format isn't very readable or diffable using standard terminal tools.
It would be interesting to ask users to classify their up/downvotes as opinion vs signal/noise ratio. Maybe that's the next evolution of leaderboard systems like HN/reddit?
What we're looking for are high signal/noise ration posts to expand the conversation into new areas that are interesting.
If the ratio is too low (eg: spam, shallow content, same old tired point), it's not an issue to downvote IMO. That helps with the current post and also encourages good behaviour in the future.
This is not the same as downvoting with a point that you personally disagree with. This is censorship and toxic to the community.
CLIs live in the same namespace as the agent, so any secrets the CLI needs access to, the agent can also exfiltrate. And access control is lightly gated by the agent's tool call policy.
For an enterprise-level deployment, it becomes quickly desirable to have a centralized MCP backbone, on which each MCP is attached to. A place you can attach policies to, log activity, and reason about access control.