memory_add_observations · Jt MCP: Risk & Policy

WHAT IT DOES

What memory_add_observations does on Jt

AI agents use memory_add_observations to create or update resources in Jt — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jt environment.

WHY IT NEEDS A POLICY

Why memory_add_observations needs a policy

This tool modifies existing entities by adding new observations/attributes to them. This is a reversible write operation (observations can presumably be removed or corrected later), not a destructive deletion. The blast radius is moderate—an agent could pollute the knowledge graph with false or misleading observations, but the data structure itself remains intact and recoverable.

From the tool's definition Tool name 'memory_add_observations' and description 'Add observations (facts, attributes, notes) to an existing entity in the knowledge graph' indicate creation/modification of data within a knowledge graph structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_add_observations Rate-limited

memory_add_observations stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_add_observations": {
      "limits": [
        {
          "counter": "memory_add_observations_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jt, so you can run agents against it safely.

FAQ

Questions about memory_add_observations

What does the memory_add_observations tool do? +

Add observations (facts, attributes, notes) to an existing entity in the knowledge graph. It is categorised as a Write tool in the Jt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_add_observations? +

Register the Jt MCP server in PolicyLayer and add a rule for memory_add_observations: 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 Jt. Nothing to install.

What risk level is memory_add_observations? +

memory_add_observations is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memory_add_observations? +

Yes. Add a rate_limit block to the memory_add_observations 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 memory_add_observations completely? +

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

memory_add_observations is provided by the Jt MCP server (@houkasaurusrex/jt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.