High Risk →

emem_trajectory

Time series for one (cell, band) over an inclusive [start, end] tslot window. Returns only what's already attested — does NOT trigger materialization. For historical backfill use emem_backfill. When to use: Call when the user asks 'how did X change over time' for a band that already has multiple ...

Part of the emem — Earth memory protocol server.

emem_trajectory can trigger actions in emem — Earth memory protocol, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE EMEM — EARTH MEMORY PROTOCOL →

Free to start. No card required.

AI agents invoke emem_trajectory to trigger processes or run actions in emem — Earth memory protocol. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

emem_trajectory can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "emem_trajectory": {
      "limits": [
        {
          "counter": "emem_trajectory_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full emem — Earth memory protocol policy for all 81 tools.

Get this rule live on your own emem — Earth memory protocol server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY EMEM — EARTH MEMORY PROTOCOL →

View all 81 tools →

These attack patterns abuse exactly the kind of access emem_trajectory gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so emem_trajectory only ever does what you allow.

SECURE EMEM — EARTH MEMORY PROTOCOL →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the emem_trajectory tool do? +

Time series for one (cell, band) over an inclusive [start, end] tslot window. Returns only what's already attested — does NOT trigger materialization. For historical backfill use emem_backfill. When to use: Call when the user asks 'how did X change over time' for a band that already has multiple historical tslots seeded. IMPORTANT differences from emem_recall: (1) trajectory does NOT auto-materialize past tslots — it returns only facts that have already been attested at this responder, so for fast-tempo bands like indices.ndwi you'll typically see ONE point at the latest tslot until an attester seeds history. (2) tslots are non-negative u64; there's no negative-offset 'last 2 years' shorthand. For LONG-TERM history questions ('flooded in last 2 years', 'forest loss since 2020') prefer either (a) a static-tempo summary band that one fact answers — surface_water.recurrence covers 1984-2021 in a single signed value, no trajectory needed — or (b) emem_backfill to materialize and sign the missing tslots in one call.. It is categorised as a Execute tool in the emem — Earth memory protocol MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on emem_trajectory? +

Register the emem — Earth memory protocol MCP server in PolicyLayer and add a rule for emem_trajectory: 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.

What risk level is emem_trajectory? +

emem_trajectory is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit emem_trajectory? +

Yes. Add a rate_limit block to the emem_trajectory 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.

How do I block emem_trajectory completely? +

Set action: deny in the PolicyLayer policy for emem_trajectory. 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.

What MCP server provides emem_trajectory? +

emem_trajectory 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.

Enforce policy on every emem — Earth memory protocol tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.