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

get_problematic_owner_mappings

A read tool on the Mapi Agent Memory MCP server.

SERVERMapi Agent Memory SOURCEcabo0m/mapi-agent-memory
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mapi-agent-memory/get-problematic-owner-mappings.md

What get_problematic_owner_mappings does on Mapi Agent Memory

AI agents call get_problematic_owner_mappings 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 get_problematic_owner_mappings is rated Low

This tool retrieves or queries problematic owner mappings from an auditable memory system. Despite the empty description limiting full context, the 'get' prefix is a strong signal of read-only retrieval with no side effects. The sibling tools (apply_*, add_*, append_*) modify memory state, but this 'get' tool appears to be for inspection only.

From the tool's definition The tool name 'get_problematic_owner_mappings' uses the 'get' verb, which indicates data retrieval. The description is empty, but the name pattern strongly suggests querying or fetching existing data about mappings rather than modifying or deleting them.

Questions about get_problematic_owner_mappings

What does the get_problematic_owner_mappings tool do? +

get_problematic_owner_mappings is a read tool on the Mapi Agent Memory MCP server. It is categorised as a Read tool in the Mapi Agent Memory MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_problematic_owner_mappings? +

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

get_problematic_owner_mappings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_problematic_owner_mappings? +

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

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

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