J
Integration · Project management
Govern your Jira agent.
Agents can create and update issues in approved projects — not bulk-delete or change workflows.
The risk
What can go wrong when an agent holds Jira.
A raw Jira token lets an agent do anything the token can — no boundary, no record. These are the actions you don't want it taking on its own.
- Bulk-deleting issues or sprints
- Editing workflows and permission schemes
- Reassigning across projects
- Exporting issue data at scale
The HiveKey policy
Scope it. Guard it. Log it.
Give the agent a role with exactly the Jira actions it needs, then guard the rest in the path.
Scope — granted
- issue.read:PROJ
- issue.create:PROJ
- issue.comment
Guard — enforced
- Scope to allow-listed projects
- Deny workflow/permission edits
- No bulk delete
The proof
Every Jira action — allowed or denied — on one trail.
jira-agent · action log live
issue_create PROJ-882 scope: issue.create allow
bulk_delete sprint#12 guard: no bulk delete deny
Put your Jira agent under one policy.
See HiveKey scope, guard, and log your Jira agent and the rest of your fleet.