VAREXIS-INDEX · Free decision guide
Delegated Agent Identity Continuity
A child agent is approved, but its credential owner, inherited consent or effective access can differ from the identity and permissions recorded at installation.
For: Identity administrators and agent operators reconciling parent credentials, resource grants and later permission changes.
Your decision: Determine which identity, consent and lifecycle facts must be reconciled before relying on a delegated agent authority declaration.
Evidence to bring
Tenant and provider; agent and parent identities; credential custody; current consent and resource grants; inheritance settings; lifecycle changes; applicable SDK and authorization profile. Use redacted references, never credentials or live tokens.
- Bind the agent, parent and tenant to the documented credential and resource-grant relationship.
- Reconcile later consent, inheritance and lifecycle changes against the current declaration.
- Check the applicable provider or optional protocol version; leave unobserved effective access unresolved.
What this evidence supports
The reviewed provider and protocol documentation separates parent credentials, child grants, later inheritance and provider-specific identity translation. It identifies evidence needed to distinguish installation approval from a current declared authority chain.
What remains unestablished
Source documentation does not inspect a tenant, verify a token, prove revocation propagation or test effective access. A sponsor, agent identifier or successful sign-in is not a universal authority grant. Optional profiles and rolling SDK behaviour require version checks.
Read the source evidence
These 9 existing records are free. Review the source version and limitations before applying a finding to your decision.
Where must an Entra agent identity obtain its authentication credentials
Identify the parent credential path rather than treating the child identifier as a credential.
Original source · Reviewed 2026-10-30. Full provenance and limitations are retained in the evidence record JSON.
Exact agent access and integrity
- Connector
https://varexis.tech/mcp/catalogue- Tool
get_publication_record- Arguments
{"record_id":"VXI-EXT-ICE09-ENTRA-AGENT-BLUEPRINT-CREDENTIAL-CUSTODY-01-v1"}- Record identifier
VXI-EXT-ICE09-ENTRA-AGENT-BLUEPRINT-CREDENTIAL-CUSTODY-01-v1- SHA-256
2316c7b9d1f05df28e7c698bf3cee88d329b090c52ad046eca08dbb606480e05
Does declaring an Entra resource inheritable grant its permissions to child agents
Check both conditions for inherited authority.
Original source · Reviewed 2026-10-30. Full provenance and limitations are retained in the evidence record JSON.
Exact agent access and integrity
- Connector
https://varexis.tech/mcp/catalogue- Tool
get_publication_record- Arguments
{"record_id":"VXI-EXT-ICE09-ENTRA-AGENT-INHERITANCE-CONSENT-TWO-CONDITIONS-01-v1"}- Record identifier
VXI-EXT-ICE09-ENTRA-AGENT-INHERITANCE-CONSENT-TWO-CONDITIONS-01-v1- SHA-256
51cb38f097c5cdeeae76424df169b1bc21e52d76d91c4216b3ac7d9ada2b5395
Can a blueprint's initial permission list describe all later inherited access
Account for later consent and inheritance changes beyond installation declarations.
Original source · Reviewed 2026-10-30. Full provenance and limitations are retained in the evidence record JSON.
Exact agent access and integrity
- Connector
https://varexis.tech/mcp/catalogue- Tool
get_publication_record- Arguments
{"record_id":"VXI-EXT-ICE09-ENTRA-AGENT-DYNAMIC-CONSENT-STATIC-INVENTORY-GAP-01-v1"}- Record identifier
VXI-EXT-ICE09-ENTRA-AGENT-DYNAMIC-CONSENT-STATIC-INVENTORY-GAP-01-v1- SHA-256
c23dcf93ede285c72aa825c1bfcb61fb26d356918a2f0fb8c5c19c8d1b5b4dc5
Which identifier receives an autonomous Entra agent app-role assignment
Distinguish the child resource principal from the blueprint client.
Original source · Reviewed 2026-10-30. Full provenance and limitations are retained in the evidence record JSON.
Exact agent access and integrity
- Connector
https://varexis.tech/mcp/catalogue- Tool
get_publication_record- Arguments
{"record_id":"VXI-EXT-ICE09-ENTRA-AGENT-APP-ROLE-PRINCIPAL-OBJECT-ID-01-v1"}- Record identifier
VXI-EXT-ICE09-ENTRA-AGENT-APP-ROLE-PRINCIPAL-OBJECT-ID-01-v1- SHA-256
fb1f9ab772c9d0ea4b41a176c992025a067b7df27af477013909e9a653ea1652
Entra agent user creation and separate resource consent
Separate account creation from consent to use the paired agent-user account.
Original source · Reviewed 2026-10-30. Full provenance and limitations are retained in the evidence record JSON.
Exact agent access and integrity
- Connector
https://varexis.tech/mcp/catalogue- Tool
get_publication_record- Arguments
{"record_id":"VXI-EXT-ICE09-ENTRA-AGENT-USER-CREATION-SEPARATE-RESOURCE-CONSENT-01-v1"}- Record identifier
VXI-EXT-ICE09-ENTRA-AGENT-USER-CREATION-SEPARATE-RESOURCE-CONSENT-01-v1- SHA-256
4db99ca7019c2d55e607bb7990971bc552117863886a09b01b220994d761a65a
Can an AgentCore callback accept consent from anyone opening its URL
Bind the authorization callback to the active user before accepting provider consent.
Original source · Reviewed 2026-10-30. Full provenance and limitations are retained in the evidence record JSON.
Exact agent access and integrity
- Connector
https://varexis.tech/mcp/catalogue- Tool
get_publication_record- Arguments
{"record_id":"VXI-EXT-ICE09-AGENTCORE-CONSENT-CALLBACK-ACTIVE-USER-BINDING-01-v1"}- Record identifier
VXI-EXT-ICE09-AGENTCORE-CONSENT-CALLBACK-ACTIVE-USER-BINDING-01-v1- SHA-256
2613a3933f3c651339c79d1c8deb5d1ba44675cdc90cf0b435a427d94e435219
Can an enterprise ID-JAG directly serve as an MCP bearer access token
Distinguish the enterprise intermediate grant from the final resource token.
Original source · Reviewed 2026-10-30. Full provenance and limitations are retained in the evidence record JSON.
Exact agent access and integrity
- Connector
https://varexis.tech/mcp/catalogue- Tool
get_publication_record- Arguments
{"record_id":"VXI-EXT-ICE09-MCP-ID-JAG-NOT-RESOURCE-ACCESS-TOKEN-01-v1"}- Record identifier
VXI-EXT-ICE09-MCP-ID-JAG-NOT-RESOURCE-ACCESS-TOKEN-01-v1- SHA-256
4b43c706d952462ef74ea7823d2fe5c4722022180a07f1901c638324bba27987
Can changing federation mappings alter access without editing IAM bindings
Review mapping changes that can change effective principals without a grant edit.
Original source · Reviewed 2026-10-30. Full provenance and limitations are retained in the evidence record JSON.
Exact agent access and integrity
- Connector
https://varexis.tech/mcp/catalogue- Tool
get_publication_record- Arguments
{"record_id":"VXI-EXT-ICE09-GCP-FEDERATION-MAPPING-CHANGE-EFFECTIVE-PRINCIPAL-01-v1"}- Record identifier
VXI-EXT-ICE09-GCP-FEDERATION-MAPPING-CHANGE-EFFECTIVE-PRINCIPAL-01-v1- SHA-256
a6ceeb000990e9581e41391aa45d3ce7eba9bd8fdd5c715d9a46b3ec41c1561a
Can a Claude SDK subagent independently weaken its parent permission mode
Check the installed runtime and effective inherited mode before relying on a sub-agent configuration.
Original source · Reviewed 2026-10-30. Full provenance and limitations are retained in the evidence record JSON.
Exact agent access and integrity
- Connector
https://varexis.tech/mcp/catalogue- Tool
get_publication_record- Arguments
{"record_id":"VXI-EXT-ICE09-CLAUDE-SDK-SUBAGENT-PERMISSION-MODE-INHERITANCE-01-v1"}- Record identifier
VXI-EXT-ICE09-CLAUDE-SDK-SUBAGENT-PERMISSION-MODE-INHERITANCE-01-v1- SHA-256
a081a5ea69a83f3e1aa0fb64cece25c0fe61f6b8b68fb4b077b10ffa43ec2be4
Connect an evidence client
Configure the two existing MCP connectors, then use the endpoint and arguments shown for each record. The original /mcp provides its frozen search and previews; /mcp/catalogue provides bounded browsing and exact access to additional published records. They are separate tool contracts, not interchangeable connections.
Canonical decision-guide JSON: records, provenance, hashes and checker selection. Enhanced natural-language search remains on HOLD. Keep credentials and private declarations local; public MCP supplies evidence and does not run licensed analysis.
When a local checker helps
Tool Admission can check supported supplied tool and authority declarations locally. It does not ingest Entra, AgentCore or Google identity exports, validate OAuth tokens, query provider permissions or enforce revocation. Prepare its existing input format separately.
Use the free guide to identify missing identity relationships and changed grants before an authority review. The separately licensed checker adds repeatable local checks of supported declarations; no new provider integration or licence right is included. These new records are outside the existing paid saved-evidence and receipt offers.
Agent Tool Admission & Permission Control
£49 + VAT · One-time internal-use licence. Separate from saved evidence and subscriptions. VAT is confirmed at checkout.
Supplied inputs: JSON declarations of GitHub, Playwright, Notion or Slack connector identity, requested and allowed actions, resources, recipients and authority; an earlier inventory supports comparison.
Local results: Structured findings about declared permission conflicts, inventory changes and missing verification, with source and content hashes.
Synthetic demonstration: A requested destination is outside the declared authority. Obtain authority evidence before relying on the plan.
Assesses supplied declarations only; no independent live-system testing, runtime enforcement, certification, verified deletion or settlement.
Read the free demonstration and licence terms · Review purchase — £49 + VAT · Existing product details
A free record supplies documented evidence. A licensed checker performs reusable local analysis of supported customer-supplied declarations. Full operational schemas, runnable examples and executable archives accompany the existing licensed package. These examples are concise synthetic excerpts, not complete operational inputs or analyses. No runtime enforcement, live-system verification or certification is supplied. Compare existing prices · Checkout and recovery terms.
Original evidence-pack section · Choose another decision guide
