Last Look Back — safety tier classification. Classifies a path + operation into LLB safety tiers: T0/READ (low) → T1/CREATE (moderate) → T2/MODIFY (high) → T3/DELETE (critical). Each tier requires additional gates. Use before any filesystem mutation.
Risk signalsAccepts file system path (path)
Part of the Ternary Intelligence Stack server.
Free to start. No card required.
AI agents may call llb_classify to permanently remove or destroy resources in Ternary Intelligence Stack. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call llb_classify in a loop, permanently destroying resources in Ternary Intelligence Stack. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"llb_classify"
]
}See the full Ternary Intelligence Stack policy for all 34 tools.
These attack patterns abuse exactly the kind of access llb_classify gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Last Look Back — safety tier classification. Classifies a path + operation into LLB safety tiers: T0/READ (low) → T1/CREATE (moderate) → T2/MODIFY (high) → T3/DELETE (critical). Each tier requires additional gates. Use before any filesystem mutation.. It is categorised as a Destructive tool in the Ternary Intelligence Stack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ternary Intelligence Stack MCP server in PolicyLayer and add a rule for llb_classify: 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 Ternary Intelligence Stack. Nothing to install.
llb_classify is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the llb_classify 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 llb_classify. 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.
llb_classify is provided by the Ternary Intelligence Stack MCP server (rfi-irfos/ternlang). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 34 Ternary Intelligence Stack tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.