create_image_modality · Memory MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_image_modality does on Memory MCP Server

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

WHY IT NEEDS A POLICY

Why create_image_modality needs a policy

This tool creates a new image modality object within the memory system, which is a reversible write operation. It does not execute external code, delete data, move money, or trigger irreversible actions. The blast radius is minimal: misuse could result in spurious image metadata being stored in memory, but this can be corrected or cleaned up using companion tools like 'cleanup_memories' or 'delete_long_term_memory'.

From the tool's definition Tool name is 'create_image_modality' and description states it creates 'an image modality object for use with memories.' The verb 'create' and the stated purpose of constructing a new object indicates data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_image_modality Rate-limited

create_image_modality 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": {
    "create_image_modality": {
      "limits": [
        {
          "counter": "create_image_modality_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 Memory MCP Server, so you can run agents against it safely.

FAQ

Questions about create_image_modality

What does the create_image_modality tool do? +

Create an image modality object for use with memories. Supports image URLs, data URIs, and optional embeddings/tags. It is categorised as a Write tool in the Memory MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_image_modality? +

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

What risk level is create_image_modality? +

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

Can I rate-limit create_image_modality? +

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

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

create_image_modality is provided by the Memory MCP Server MCP server (win10ogod/memory-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.