What an agent can do
What your agent can read, what it can prepare, and what it can never do on Fransys.
Your projects, services, settings, clusters, logs and metrics, depending on its key’s rights. Billing only if the key allows it (Also read billing). Secrets stay masked.
Prepare plans
Section titled “Prepare plans”The agent submits plans, which land in Plans, awaiting your decision. It can edit or cancel a plan it prepared as long as it isn’t approved, and propose to undo a plan that has run.
Never: approve or run
Section titled “Never: approve or run”The MCP has no tool to approve or run a plan. A person on your team approves each plan in the console, which then runs it. That’s the airlock: the agent prepares, a human decides.
What the agent doesn’t do either
Section titled “What the agent doesn’t do either”- It doesn’t change your Git repository. If something needs changing (a port, a variable read by your entrypoint), it tells you what to change.
- It doesn’t work out a price on its own: it goes through Fransys’s estimate.
A key’s rights
Section titled “A key’s rights”An agent key only grants read access: projects, services, logs, clusters, cloud accounts, and billing if you ticked it. Remove a key to cut an agent’s access right away. See Connect an agent.
Coming soon: team and approval rules
Section titled “Coming soon: team and approval rules”The Access page will bring together connected agents, the people on your team and their role, and approval rules, for example a second person to run a plan prepared by an agent. In the meantime, connect your agents from Connect.