Three-encoder change ensemble: compute the cosine change between the two most-recent DISTINCT vintages for each of the Clay, Prithvi, and Tessera embeddings at the cell, then vote each encoder's change against consensus_threshold (registry default 0.15). Returns each encoder's change magnitude, i...
Part of the emem — Earth memory protocol server.
Free to start. No card required.
AI agents call emem_triple_consensus to retrieve information from emem — Earth memory protocol without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though emem_triple_consensus only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"emem_triple_consensus": {}
}
}See the full emem — Earth memory protocol policy for all 81 tools.
These attack patterns abuse exactly the kind of access emem_triple_consensus gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Three-encoder change ensemble: compute the cosine change between the two most-recent DISTINCT vintages for each of the Clay, Prithvi, and Tessera embeddings at the cell, then vote each encoder's change against consensus_threshold (registry default 0.15). Returns each encoder's change magnitude, its vote, and the consensus verdict (how many of the three agree change happened). Degrades to a signed inconclusive when the GPU sidecar is unreachable or a cell lacks two distinct vintages for the encoders. When to use: Call when the user wants a robust, model-agnostic 'did this place change' answer backed by three independent foundation encoders rather than one — e.g. cross-checking a single-encoder alert, or auditing change with consensus voting. Surface the per-encoder change + the vote count. When only one encoder has two vintages the verdict is honest about the thin evidence. For a single-encoder vector delta use emem_state_diff; for the NDVI+embedding proxy use emem_deforestation_alert.. It is categorised as a Read tool in the emem — Earth memory protocol MCP Server, which means it retrieves data without modifying state.
Register the emem — Earth memory protocol MCP server in PolicyLayer and add a rule for emem_triple_consensus: 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 emem — Earth memory protocol. Nothing to install.
emem_triple_consensus 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 emem_triple_consensus 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 emem_triple_consensus. 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.
emem_triple_consensus is provided by the emem — Earth memory protocol MCP server (oci:ghcr.io/vortx-ai/emem:latest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 81 emem — Earth memory protocol 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.