Tool Access Is Not Data Authority

Part I

Problem Definition

A tool being visible, schema-valid, and technically able to reach a record does not prove that the current principal authorized this concrete resource, parameter, purpose, and destination [R1] [R2].

This note treats tool access is not data authority as a bounded control question. It does not infer universal product behavior from a paper, standard, interface screenshot, or single test. A demonstrated result applies only to the cited configuration; an authoritative source defines a requirement or design direction but does not certify an implementation. ACE therefore asks whether the tested system can produce the required behavior and evidence under declared versions, policies, topology, identities, and failure conditions.

The operational distinction is between a claim and a control that can be re-performed. The positive control is: User A reads customer 123 in tenant A through a narrowly scoped read tool. The adversarial condition is: Injected content changes the parameters to customer 999 in tenant B while the service account remains technically capable. A useful result must show both that authorized work remains possible and that the prohibited path is stopped before an irreversible side effect. Missing fields are classified as insufficient evidence, not silently converted into a pass.

Real-world impact

• A legitimate service credential can conceal an unauthorized purpose or cross-tenant read.
• Schema validation may make a dangerous call look well formed without making it authorized.
• A control claim without versioned evidence can mislead procurement, audit, incident response, and system owners.
• Failing closed without a positive control can conceal a denial-of-service design rather than demonstrate trustworthy behavior.

Part II

Mitigation Direction

Research-backed direction

1. 01
   research proposed

   Treat a tool allowlist as a capability gate followed by parameter-level authorization [R1] [R3].

2. 02
   research proposed

   Use resource-bound, minimum-scope credentials and prohibit token passthrough [R4] [R1].

3. 03
   research proposed

   Enforce authorization in the downstream service rather than relying on model self-restraint [R2].

LogionOS engineering mapping

Implementation hypotheses only. No production validation is claimed.

1. 01
   implementation hypothesis

   Add a versioned policy object for tool access is not data authority and keep its decision inputs outside model-writable context.

2. 02
   implementation hypothesis

   Generate a signed technical receipt linking actor, request, policy version, decision, enforcement point, and observed outcome.

3. 03
   implementation hypothesis

   Export missing evidence explicitly as insufficient evidence and limit every claim to the tested configuration.

Part III

Consequences and Research Agenda

Consequences

• A legitimate service credential can conceal an unauthorized purpose or cross-tenant read.
• Schema validation may make a dangerous call look well formed without making it authorized.
• A failed acceptance test requires the related capability claim to remain not demonstrated or insufficient evidence.
• A passing test supports only the declared configuration and does not establish universal safety.

Second-order effects

• Stronger enforcement can increase latency, state, operational dependencies, and legitimate denials.
• More evidence can increase privacy and retention exposure unless raw content is minimized and access-controlled.
• A detector or policy service can become a new failure point and must have explicit fail behavior.
• Attackers may adapt to published checks, so the public test direction should be paired with private regression variants.

Limitations

• Several cited AI-agent and reasoning-security sources are preprints or bounded experiments; they are identified as such in the references.
• The proposed ACE acceptance test has not yet been run across all incumbent and AI-native implementations.
• Cryptographic integrity proves that an artifact was not altered after commitment; it does not prove that the artifact was true, complete, or correctly interpreted.
• Legal and contractual applicability remains deployment- and jurisdiction-specific.

Open research questions

1. How should derived-data authority persist after aggregation?
2. How can offline tools verify short-lived authority without accepting stale grants?
3. Which evidence fields are mandatory for a demonstrated result, and which may be not applicable?
4. How should continuous regression detect policy, model, tool, and provider drift after the initial test?

Sources

References

1. [R1]
   MCP Security Best Practices

   published · authoritative-standard

2. [R2]
   OWASP LLM06: Excessive Agency

   published · authoritative-standard

3. [R3]
   Capability Gates Are Not Authorization

   preprint · original-paper

4. [R4]
   RFC 8707: Resource Indicators for OAuth 2.0

   published · authoritative-standard

Record

Publication Record

Recommended citation

Ma, Chris. “Tool Access Is Not Data Authority.” ACE Research Note ACE-RN-2026-006, v1.0, 2026.

Corrections

No corrections recorded.

Organizational disclosure

ACE Research and LogionOS share organizational affiliation. LogionOS mappings in this note are implementation hypotheses, not independently validated product claims.

Evidence boundary

This note synthesizes cited public research and defines an ACE acceptance direction. It does not report a completed cross-vendor experiment unless explicitly stated, and it contains no private ACE prompts, holdout identifiers, customer data, or raw model responses.