Get reference documentation for available Nucleus commands.
AI agents call nucleus_commands 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 or queries reference documentation about available Nucleus commands. It has no side effects—it does not execute commands, modify data, delete anything, or trigger external operations. It is purely informational, making it a Read category tool with low severity since documentation retrieval poses minimal security risk even if accessed by an untrusted agent.
From the tool's definition Tool name 'nucleus_commands' with description 'Get reference documentation for available Nucleus commands' indicates retrieval of documentation without modification or execution.
Documented attack patterns abuse exactly the kind of access nucleus_commands 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 nucleus_commands:
{
"version": "1",
"default": "deny",
"tools": {
"nucleus_commands": {}
}
}nucleus_commands 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 reference documentation for available Nucleus commands. 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 nucleus_commands: 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.
nucleus_commands 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 nucleus_commands 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 nucleus_commands. 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.
nucleus_commands 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.