list_project_key_aliases
List configured project_key aliases. Aliases are only used when project_key_mode='aliases'.
This record as markdown: /tools/mapi-agent-memory/list-project-key-aliases.md
What list_project_key_aliases does on Mapi Agent Memory
AI agents call list_project_key_aliases to retrieve information from Mapi Agent Memory without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_project_key_aliases is rated Low
This tool retrieves and lists alias configurations. The word 'list' is a classic Read operation pattern, and there is no indication of creating, modifying, deleting, or executing anything. The tool simply queries and returns existing alias mappings. Blast radius is minimal as it only exposes configuration metadata that is likely non-sensitive inventory data.
From the tool's definition Tool name 'list_project_key_aliases' and description 'List configured project_key aliases' indicate retrieval/query of existing configuration data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_project_key_aliases 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 list_project_key_aliases, this is the rule to start with:
list_project_key_aliases is read-only, so it stays allowed. 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 list_project_key_aliases call is checked against it from then on.
Questions about list_project_key_aliases
List configured project_key aliases. Aliases are only used when project_key_mode='aliases'. It is categorised as a Read tool in the Mapi Agent Memory MCP Server, which means it retrieves data without modifying state.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for list_project_key_aliases: 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.
list_project_key_aliases is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_project_key_aliases 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 list_project_key_aliases. 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.
list_project_key_aliases 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