Write a memory entry to one of three layers: working (hot context, TTL 1h), session (flow patterns, TTL 24h), or core (identity anchors, never evicted). Annotate each entry with a trit confidence score (+1 affirm / 0 tend / -1 reject). Session and core writes are automatically compressed via tern...
Part of the Ternary Intelligence Stack MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use trit_mem_write to create or modify resources in Ternary Intelligence Stack. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call trit_mem_write repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Ternary Intelligence Stack.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
trit_mem_write:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Ternary Intelligence Stack policy for all 30 tools.
Agents calling write-class tools like trit_mem_write have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Write a memory entry to one of three layers: working (hot context, TTL 1h), session (flow patterns, TTL 24h), or core (identity anchors, never evicted). Annotate each entry with a trit confidence score (+1 affirm / 0 tend / -1 reject). Session and core writes are automatically compressed via ternary sparsity (low-information sentences stripped). Premium: memory is stored server-side — no state blob required.. It is categorised as a Write tool in the Ternary Intelligence Stack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for trit_mem_write. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ternary Intelligence Stack MCP server.
trit_mem_write is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the trit_mem_write rule in your Intercept 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 Intercept policy for trit_mem_write. 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.
trit_mem_write is provided by the Ternary Intelligence Stack MCP server (rfi-irfos/ternlang). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept