Skip to main content
Back to Skill Library
Agent governance workflow library

Agent Tool Permission Lease Review

Turn temporary agent tool authority into a lease record with expiry, closure, renewal routing, stale replay tests, revocation evidence, and audit gates.

This is a complete workflow library with 5 individual skills. Download the full library or pick the specific skill folder your team needs first.

Individual skills in this library

Use one skill at a time, or keep the full workflow together.

Some AI tools expect one skill folder per upload. Download the full library when you want the whole workflow, or download an individual skill when you only need one job done.

Skill 1

Permission lease record writer

Use when an agent, subagent, MCP server, browser profile, repository workflow, connector, or automation needs a temporary tool permission record before access is enabled.

Skill 2

Expiry and closure condition mapper

Use when temporary agent authority needs both a time-based expiry and a work-based closure condition tied to a task, subgoal, ticket, issue, session, repository path, or customer record.

Skill 3

Lease renewal request router

Use when an agent requests more time, wider target scope, stronger operations, new tools, delegated child access, or repeated use after a temporary permission lease is near expiry, expired, or closed.

Skill 4

Stale authority replay tester

Use when a workflow needs a test that proves expired, closed, revoked, superseded, or wrong-context agent tool authority cannot be reused for a side effect.

Skill 5

Revocation and audit gatekeeper

Use when a temporary agent permission lease needs revocation evidence, emergency disablement, audit records, release gating, or incident follow-up before production trust.

Security fit check

Is the public Agent Tool Permission Lease Review library enough, or does this need deeper review?

Use the public library when the workflow is low-risk, the inputs are already sanitized, and a team member can review the output before it reaches a buyer or customer.

Do deeper review when this workflow touches real tools, data sources, role ownership, approval paths, or customer-facing output.

Tool authorizationAI OperationsSecurityPlatform EngineeringTooling OwnerWorkflow Owner

Good deeper-review trigger signals

  • The workflow touches customer, prospect, CRM, proposal, security, pricing, or campaign data.
  • Different teams disagree on the approved source of truth.
  • The AI output could become customer-facing, revenue-impacting, or compliance-sensitive.
  • You need reusable eval checks before asking more people to use the workflow.