Example agent
Access requests: checked against policy, ready for one-click approval
An example Sigma agent that checks access requests against your access policy and the requester's role, flags conflicts and prepares the change for the access owner.
· 1 min read · By Sigma editorial team
- Function
- IT and customer service
Anatomy of this agent
An agent is instructions, skills, tools and knowledge. For each request it decides which of them to use; there is no fixed flow. Sensitive actions wait for a person’s approval.
Instructions (excerpt)
You prepare access requests for approval. For each new request, read it from the service desk, look up the requester's role and current access, and check the request against the access policy with Company Search. Flag segregation-of-duties conflicts, missing manager approval and access broader than the role needs, quoting the policy. Write a one-paragraph recommendation for the access owner. Propose the change only after the owner approves; never grant access yourself.
Skills
- access-policy-rules: role catalogue, segregation-of-duties pairs and recommendation format (SKILL.md)
Tools
- get_access_request (REST tool, your ITSM API)
- get_user_access (REST tool, your identity system API, read-only)
- add_recommendation (REST tool, your ITSM API)
- Company Search (native tool, over Spaces)
Knowledge (Spaces)
- Access policy and role catalogue (Space, folder restricted to IT security)
Needs a person’s approval
- add_recommendation: always
What this agent does
Access requests pile up because each one needs someone to check the role, the policy and the person's existing access before an owner can approve. Rushed checks lead to over-privileged accounts.
The agent does the checking and writes the recommendation. The access owner approves, and nothing is granted without them.