1 min lesson
What an enterprise agent needs
Explain how rules, outside context and execution controls shape an enterprise agent.
Step 1 of 2
A model is only one part of an enterprise agent.
The same model can behave very differently depending on its instructions, the systems it can reach and the actions it can take. An FDE configures those parts so a team gets consistent results without giving the agent unnecessary access.
Review the setup in three parts.
- Knowledge covers the team's standards and instructions.
- Context covers the information the agent can read inside and outside the repository.
- Capability covers the actions and systems the agent can use.
If an agent produces a poor result, check these parts separately. It may have missed a rule, lacked relevant context or held more access than the task required. Each cause has a different fix.
We do not rely on the model alone. We define its instructions, limit the context it can reach and restrict the actions it can take. We add autonomy only after the controls work in practice.
- Plane
- Knowledge
- Mechanism
- Project RulesVersion-controlled instructions in the repo that every Cursor agent interaction inherits, so standards are encoded once. Press Enter for the full definition. and AGENTS.md
- Failure if you skip it
- The agent misses team conventions and produces inconsistent changes
- Plane
- Context
- Mechanism
- MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. servers and admin controls
- Failure if you skip it
- The agent guesses about external systems or reads from an unapproved source
- Plane
- Capability
- Mechanism
- Run Modes, hooks, sandboxing and VM isolation
- Failure if you skip it
- The agent can run an unsafe action or send data where it should not
| Plane | Mechanism | Failure if you skip it |
|---|---|---|
| Knowledge | Project RulesVersion-controlled instructions in the repo that every Cursor agent interaction inherits, so standards are encoded once. Press Enter for the full definition. and AGENTS.md | The agent misses team conventions and produces inconsistent changes |
| Context | MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. servers and admin controls | The agent guesses about external systems or reads from an unapproved source |
| Capability | Run Modes, hooks, sandboxing and VM isolation | The agent can run an unsafe action or send data where it should not |
Review knowledge, context and capability before increasing agent access.