memory_put

Insert or update a context-memory entry. Use

SERVERIconnect SOURCEiconnect-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/memory-put.md

WHAT IT DOES

What memory_put does on Iconnect

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

RISK

Why memory_put is rated Medium

This tool creates or modifies data (memory entries) in a reversible manner. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial). The 'Insert or update' operation is characteristic of Write category tools.

From the tool's definition Tool name 'memory_put' and description 'Insert or update a context-memory entry' indicate creation or modification of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs memory_put safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory_put, this is the rule to start with:

memory_put Rate-limited

memory_put 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_put": {
      "limits": [
        {
          "counter": "memory_put_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every memory_put call is checked against it from then on.

FAQ

Questions about memory_put

What does the memory_put tool do? +

Insert or update a context-memory entry. Use. It is categorised as a Write tool in the Iconnect 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_put? +

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

What risk level is memory_put? +

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

Can I rate-limit memory_put? +

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

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

memory_put is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

team_manager_write_memory on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →