# AWS TOLAP

> Updated 2026-09-23 · type: tool · category: integration-orchestration · status: active · rev 1

AWS TOLAP enforces column/row/field access control at the tool layer so data-access policies follow the data across MCP, LangChain and Bedrock Agents.

- Open source: yes (Apache-2.0)
- Self-hostable: yes
- Pricing model: free
- Best for: A security or RevOps engineer giving agents access to sensitive data who needs object-level (column/row/field) policies enforced at the tool boundary, consistently across whichever agent framework or protocol calls the data.
- Last verified: 2026-09-23

- **Canonical:** https://gtmstacker.com/registry/tool/aws-tolap/
- **Source:** [AWS Open Source Blog · Phillip Spies](https://github.com/awslabs/tolap)
- **Tags:** integration-orchestration, mcp-agents, self-hostable, access-control, governance, protocol
- **Repository:** https://github.com/awslabs/tolap

## Is AWS TOLAP open source?

Yes, AWS TOLAP is open source under the Apache-2.0 license.

## How much does AWS TOLAP cost?

AWS TOLAP is free to use.

## Can I self-host AWS TOLAP?

Yes, AWS TOLAP can be self-hosted (the source is available under the Apache-2.0 license).


---

Apache-2.0 protocol from AWS Labs — the Tool-Object Level Access Protocol — that enforces object-level access control (column, row, field) around the tool/function layer so data-access policies travel with the data rather than the agent. It is protocol-agnostic across MCP, LangChain, Bedrock Agents and Semantic Kernel, and ships enforcement SDKs for .NET, Python and TypeScript plus a reference policy server. It is a legitimate first-party AWS launch that is almost entirely undiscovered so far (5 stars, null repo description).

## Provenance

- Apache-2.0 (OSI-open); 5 stars, created 2026-07-28, last push 2026-09-17; object-level (column/row/field) access control enforced at the tool/function layer, protocol-agnostic across MCP, LangChain, Bedrock Agents and Semantic Kernel, shipping enforcement SDKs for .NET/Python/TypeScript plus a reference policy server (WebFetch 2026-09-23).
- Confirmed via the official AWS Open Source Blog (Phillip Spies, 2026-09-22); surfaced through the 2026-09-23 X viral-posts brief (official @AWSOpen).
- Anti-hype note: this is a real AWS Labs launch but almost undiscovered — 5 stars, null GitHub description. Presented as an early first-party release, not a viral or established standard.
- Curated from the GTM Stacker signal registry (2026-09-23 pass); license/facts independently verified 2026-09-23.

## Why it matters for a GTM stack

The governance gap in agentic data access is that policy usually attaches to the agent — grant it a scope, hope it stays inside. TOLAP inverts that: the access rule binds to the object (a column, a row, a field) and is enforced at the tool/function boundary, so the same policy holds no matter which agent or framework makes the call. For a RevOps or security team letting agents touch customer, deal or PII data, that is the plumbing that lets you say "agents may read these fields and not those" and have it enforced consistently across MCP, LangChain and Bedrock Agents. The honest read: it is a brand-new AWS Labs launch with essentially no traction yet, and it is a protocol with SDKs — the value only appears once you wire the enforcement into your own tool layer.