PlatformEngr® Platform fundamentals course

Cheat notes · Module 05 · What the platform offers

Agents: the platform's second kind of user

A five-minute review for when you have done this module and want it back in your head. Open the full module for the steps and the lab, or the full text to print.

The idea

Coding agents are users of the platform. They get the same paths as people, with their own identity, an interface they can call, written instructions, and limits on functionality, permissions and autonomy.

Remember

  • OWASP LLM06:2025 Excessive Agency: excessive functionality, permissions and autonomy.
  • Non-human identity: the agent acts as itself, never with a person's token (A3).
  • default: deny; a non-read action in prod needs approval: human (A1, A7).
  • Every agent has an owner team, a monthly budget and an audit log (A5, A6).
  • MCP: an open standard for connecting AI applications to external systems.
  • AGENTS.md: "a README for agents", shipped in the golden-path template.
  • Capabilities for agents need api, mcp, git or cli (C3); policy rules need api or mcp (A4).

Pitfalls

  • A personal token gives the agent all of that person's access and their name in the audit log (A3).
  • Removing the approval to fix a slow wait (A7): fix the wait instead.
  • An agent that guesses the build command is missing context, not permissions.

agents/policy.yaml (part)

default: deny
agents:
  - id: checkout-coding-agent
    owner: checkout
    identity:
      kind: non-human
      name: agent:checkout-coding
    budget:
      monthlyEur: 400
    audit: true
    allow:
      prod:
        - action: deploy
          capability: deploy
          approval: human

Test yourself

Answer in your head first, then open the answer.

Name the three causes of excessive agency.

Excessive functionality, excessive permissions, excessive autonomy.

Why its own identity?

It can be scoped, audited and revoked without locking a person out.

Where do agents learn the path?

From AGENTS.md in the repository, copied from the template.

What may an agent do in prod without approval here?

Read: logs, metrics, the catalog.

Where module 05 leaves you: platform.yaml has a third user, coding-agent, of kind agent. Nine capabilities list agents as users. The path is for: [humans, agents] and names golden-paths/new-service/AGENTS.md. agents/policy.yaml passes the check with two agents.