Get current session status including document info, active handles, and timeout.
AI agents call lattice_status 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 is a query/inspection tool that retrieves information about the current session state (document info, active handles, timeout). It performs no mutations, executions, or deletions. It is purely informational and read-only in nature.
From the tool's definition Tool name 'lattice_status' and description 'Get current session status' indicates retrieval of state information without modification or execution of external operations. No side effects or data changes.
Documented attack patterns abuse exactly the kind of access lattice_status 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_status:
{
"version": "1",
"default": "deny",
"tools": {
"lattice_status": {}
}
}lattice_status 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 current session status including document info, active handles, and timeout. 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_status: 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_status 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_status 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_status. 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_status 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.