Issue
Agent Gets Conflicting Tool Authority
An agent receives conflicting authority signals about whether, when, or how it may use a tool, connector, function, or integration.
What This Looks Like
The agent receives mixed signals about tool authority. One rule, prompt, permission, policy, or workflow state may allow tool use while another blocks it, narrows it, requires approval, or describes a different allowed mode. The agent may call the tool inconsistently, refuse unexpectedly, ask for permission repeatedly, or choose the wrong action boundary.
Why It Matters
Tool authority controls operational behavior. If the agent receives conflicting authority signals, users cannot tell whether tool use is allowed, blocked, pending approval, or limited to a specific mode. This can cause failed tool calls, skipped actions, unauthorized actions, or unstable agent behavior across similar tasks.
Structural Signal
Multiple authority sources govern the same tool action with incompatible requirements. The issue is not simply that the tool failed; it is that the agent’s authority to use the tool is conflicted.
Common Triggers
- Prompt instructions permit a tool while policy or product mode blocks it
- Tool permissions exist but workflow approval is still required
- MCP or connector rules differ from user-facing instructions
- The agent has read authority but not action authority
- A hidden rule narrows tool use without exposing the boundary
- Tool schema, permission state, and workflow role describe different authority levels
When to Use This Issue
Use this Issue when an agent receives conflicting authority signals about whether, when, or how it may use a tool or integration.
When Not to Use This Issue
Do not use this Issue when the tool is simply unavailable, missing inputs, or called with the wrong schema. This Issue applies when the conflict is specifically about tool authority.
Category
Primary Pattern
Declared Patterns
Authority Collision
A structural condition where multiple authorities claim governance over the same region without a declared precedence or resolution rule.
Interface Mismatch
A structural condition where observed interface behavior, shape, or exchange differs from the declared interface contract.
Authority Shadowing
A structural condition where a declared authority is functionally overridden by another authority without an explicit override rule.
Derived Primary Lenses
Authority Overlay Lens
Maps declared authority hierarchies onto observed structure to detect absence, override, or conflict.
Conflict Lens
Detects mutually incompatible constraints, claims, states, or declarations that cannot be simultaneously satisfied.
Interface Contract Lens
Compares declared interface structure to observed runtime structure to detect contract deviations.
Derived Secondary Lenses
Invariant Lens
Verifies that declared invariants are structurally enforceable and not contradicted by observed structure.
Normalization Lens
Transforms structurally equivalent variants into a canonical form to prevent false divergence.
Reconciliation Lens
Evaluates whether structural changes align with declared authority updates, version changes, or reconciliation rules.
Search Intents
- agent gets conflicting tool authority
- AI agent tool authority conflict
- tool permission conflicts with prompt
- agent allowed and blocked from tool
- conflicting MCP tool authority
- agent tool access rules conflict