upsert_project_key_alias
Create or update one project_key alias for explicit alias-mode retrieval.
This record as markdown: /tools/mapi-agent-memory/upsert-project-key-alias.md
What upsert_project_key_alias does on Mapi Agent Memory
AI agents use upsert_project_key_alias 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_project_key_alias is rated Medium
The tool performs reversible data modification (creating or updating an alias mapping). While aliases could potentially affect system behavior or access control, the operation itself is not destructive (data can be updated or removed) and does not execute code or trigger external side effects. The 'upsert' semantic and context within a memory governance system indicates Write-level risk.
From the tool's definition Tool description states 'Create or update one project_key alias', which are write operations that modify data reversibly. The 'upsert' operation (create or update) is characteristic of Write category tools.
Attacks that exploit this kind of access
The rule that runs upsert_project_key_alias 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 upsert_project_key_alias, this is the rule to start with:
upsert_project_key_alias 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 upsert_project_key_alias call is checked against it from then on.
Questions about upsert_project_key_alias
Create or update one project_key alias for explicit alias-mode retrieval. 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 upsert_project_key_alias: 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.
upsert_project_key_alias 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 upsert_project_key_alias 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 upsert_project_key_alias. 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.
upsert_project_key_alias 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