New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

upsert_owner_directory_item

A write tool on the Mapi Agent Memory MCP server.

SERVERMapi Agent Memory SOURCEcabo0m/mapi-agent-memory
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/mapi-agent-memory/upsert-owner-directory-item.md

What upsert_owner_directory_item does on Mapi Agent Memory

AI agents use upsert_owner_directory_item 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 upsert_owner_directory_item is rated Medium

The 'upsert' pattern is characteristic of Write operations that create or modify data reversibly. While the empty description reduces confidence, the semantic meaning of upsert combined with 'directory_item' suggests data modification within an agent memory governance system.

From the tool's definition Tool name 'upsert_owner_directory_item' indicates a create/update operation (upsert = update or insert). The description is empty, limiting specificity.

Questions about upsert_owner_directory_item

What does the upsert_owner_directory_item tool do? +

upsert_owner_directory_item 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.

How do I enforce a policy on upsert_owner_directory_item? +

Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for upsert_owner_directory_item: 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.

What risk level is upsert_owner_directory_item? +

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

Can I rate-limit upsert_owner_directory_item? +

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

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

upsert_owner_directory_item 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mapi Agent Memory's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.