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

run_memory_linking_pass

Deterministycznie tworzy brakujace linki grafu pamieci.

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/run-memory-linking-pass.md

What run_memory_linking_pass does on Mapi Agent Memory

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

The tool creates missing links in the memory graph, which is a write/modification operation on the memory store. It does not appear to delete or overwrite existing data, just adds new relationships. Severity is medium because incorrect linking could corrupt agent memory context. Confidence is moderate because the description is in Polish and brief, leaving some ambiguity about full scope.

From the tool's definition 'tworzy brakujace linki grafu pamieci' (creates missing memory graph links)

Questions about run_memory_linking_pass

What does the run_memory_linking_pass tool do? +

Deterministycznie tworzy brakujace linki grafu pamieci. 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 run_memory_linking_pass? +

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

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

Can I rate-limit run_memory_linking_pass? +

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

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

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

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