set_owner_target_active

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/set-owner-target-active.md

WHAT IT DOES

What set_owner_target_active does on Mapi Agent Memory

AI agents use set_owner_target_active 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.

RISK

Why set_owner_target_active is rated Medium

The name pattern 'set_*_active' indicates a state modification operation (Write category). No destructive language (delete, drop, purge) or financial operations are evident. However, empty description reduces confidence. Given the governance/memory context and sibling tools that apply changes reversibly, this appears to be a write operation that modifies metadata or status without permanent deletion.

From the tool's definition Tool name 'set_owner_target_active' suggests modification of ownership/activation state. Server context indicates memory and governance operations with 'apply_*' and 'add_*' sibling tools that perform reversible state changes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_owner_target_active 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 set_owner_target_active, this is the rule to start with:

set_owner_target_active Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_owner_target_active": {
      "limits": [
        {
          "counter": "set_owner_target_active_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every set_owner_target_active call is checked against it from then on.

FAQ

Questions about set_owner_target_active

What does the set_owner_target_active tool do? +

set_owner_target_active 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 set_owner_target_active? +

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

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

Can I rate-limit set_owner_target_active? +

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

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

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

KEEP EXPLORING

More on Mapi Agent Memory, and thousands of servers like it.

This server

All 252 Mapi Agent Memory tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →