make_dir
A write tool on the Mapi Agent Memory MCP server.
This record as markdown: /tools/mapi-agent-memory/make-dir.md
What make_dir does on Mapi Agent Memory
AI agents use make_dir to create or update resources in Mapi Agent Memory, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mapi Agent Memory environment.
Why make_dir is rated Medium
The name 'make_dir' strongly implies creating a new directory, which is a Write operation (reversible creation). However, the empty description lowers confidence. Given the server context involves file and memory management (e.g., 'append_file_text'), directory creation fits the Write category.
From the tool's definition Tool name 'make_dir' suggests directory creation; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs make_dir safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For make_dir, this is the rule to start with:
make_dir 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every make_dir call is checked against it from then on.
Questions about make_dir
make_dir is a write tool on the Mapi Agent Memory MCP server. It is categorised as a Write tool in the Mapi Agent Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for make_dir: 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 Mapi Agent Memory. Nothing to install.
make_dir is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the make_dir 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.
Set action: deny in the PolicyLayer policy for make_dir. 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.
make_dir is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
This server
Across the catalogue