Get full data from a handle when you need to inspect actual results. USE THIS WHEN: - You need to see actual content to make decisions - You want to verify what
AI agents call lattice_expand 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 inspects data from a handle for verification purposes. There is no indication of modification, deletion, execution of code, or financial operations. It is a passive data retrieval function, making it clearly a Read category tool with low severity.
From the tool's definition Tool description states 'Get full data from a handle when you need to inspect actual results' and 'You need to see actual content to make decisions' — indicates retrieval/inspection without modification.
Documented attack patterns abuse exactly the kind of access lattice_expand 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_expand:
{
"version": "1",
"default": "deny",
"tools": {
"lattice_expand": {}
}
}lattice_expand 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.
Get full data from a handle when you need to inspect actual results. USE THIS WHEN: - You need to see actual content to make decisions - You want to verify what. 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_expand: 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_expand 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_expand 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_expand. 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_expand 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.