rollout_owner_catalog_to_project

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/rollout-owner-catalog-to-project.md

WHAT IT DOES

What rollout_owner_catalog_to_project does on Mapi Agent Memory

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

The name implies a write/deploy operation — rolling out catalog data to a project. This would create or update records in the project context. However, the description is empty and uninformative, which significantly reduces confidence. Given sibling tools involve memory governance, lifecycle management, and consolidation, this tool likely writes or applies catalog ownership data.

From the tool's definition Tool name 'rollout_owner_catalog_to_project' suggests deploying or propagating an owner catalog to a project scope.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

rollout_owner_catalog_to_project Rate-limited

rollout_owner_catalog_to_project 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": {
    "rollout_owner_catalog_to_project": {
      "limits": [
        {
          "counter": "rollout_owner_catalog_to_project_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 rollout_owner_catalog_to_project call is checked against it from then on.

FAQ

Questions about rollout_owner_catalog_to_project

What does the rollout_owner_catalog_to_project tool do? +

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

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

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

Can I rate-limit rollout_owner_catalog_to_project? +

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

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

rollout_owner_catalog_to_project 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

create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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