create_memory_entry · RoadBoard MCP: Risk & Policy

WHAT IT DOES

What create_memory_entry does on RoadBoard

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

WHY IT NEEDS A POLICY

Why create_memory_entry needs a policy

This tool creates (writes) new memory entries within a project. Writing is reversible—memory entries can typically be edited or deleted by authorized users. There is no indication this operation destroys data, executes arbitrary code, or involves financial transactions. The blast radius is limited to project state modification within the defined system.

From the tool's definition Tool name 'create_memory_entry' and description 'Create a new memory entry' indicate data creation. The server description states it provides 'MCP tools for agents to read and write project state.' Memory entries are additive, reversible data structures.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_memory_entry Rate-limited

create_memory_entry 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_memory_entry": {
      "limits": [
        {
          "counter": "create_memory_entry_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 RoadBoard, so you can run agents against it safely.

FAQ

Questions about create_memory_entry

What does the create_memory_entry tool do? +

Create a new memory entry in a project. Use. It is categorised as a Write tool in the RoadBoard 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_memory_entry? +

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

What risk level is create_memory_entry? +

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

Can I rate-limit create_memory_entry? +

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

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

create_memory_entry is provided by the RoadBoard MCP server (maless88/roadboard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.