Show current handle bindings. Returns all active handles with their stubs: $grep_error: Array(500) [preview of first item...] $filter: Array(50) [preview...] RESULTS: -> $filter Use this to see what data you have available before deciding what to expand.
AI agents call lattice_bindings to retrieve information from Lattice without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays the current state of variable bindings in the Lattice environment. It has no capability to modify, execute, or delete data—it only queries and presents existing information. This makes it a pure Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'lattice_bindings' and description 'Show current handle bindings' indicate a query/inspection operation.
Documented attack patterns abuse exactly the kind of access lattice_bindings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lattice, and nothing reaches the server without passing your rules. This is the rule we recommend for lattice_bindings:
{
"version": "1",
"default": "deny",
"tools": {
"lattice_bindings": {}
}
}lattice_bindings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show current handle bindings. Returns all active handles with their stubs: $grep_error: Array(500) [preview of first item...] $filter: Array(50) [preview...] RESULTS: -> $filter Use this to see what data you have available before deciding what to expand. It is categorised as a Read tool in the Lattice MCP Server, which means it retrieves data without modifying state.
Register the Lattice MCP server in PolicyLayer and add a rule for lattice_bindings: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Lattice. Nothing to install.
lattice_bindings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the lattice_bindings rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for lattice_bindings. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
lattice_bindings is provided by the Lattice MCP server (yogthos/matryoshka). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Lattice tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Lattice tools catalogued and risk-classified — across an index of 42,500+ MCP servers.