run_sandman_gemma_hygiene

Run Gemma-style Sandman hygiene for low-risk validated actions only. Semantic archive stays review-only.

SERVERMapi Agent Memory SOURCEcabo0m/mapi-agent-memory

High RISK CLASS

Category Execute

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/run-sandman-gemma-hygiene.md

WHAT IT DOES

What run_sandman_gemma_hygiene does on Mapi Agent Memory

AI agents invoke run_sandman_gemma_hygiene to trigger actions in Mapi Agent Memory. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why run_sandman_gemma_hygiene is rated High

This tool executes a hygiene process (Sandman) that modifies agent memory. While scoped to 'low-risk validated actions only', the execution of memory transformation operations qualifies as Execute rather than Write because it triggers an external process/service (Gemma-style hygiene) whose side effects are conditional on runtime validation state.

From the tool's definition Tool name includes 'run' indicating command execution. Description specifies 'Run Gemma-style Sandman hygiene' which triggers an external hygiene operation whose effects depend on what actions are classified as 'validated'.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

run_sandman_gemma_hygiene Rate-limited

run_sandman_gemma_hygiene stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_sandman_gemma_hygiene": {
      "limits": [
        {
          "counter": "run_sandman_gemma_hygiene_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 run_sandman_gemma_hygiene call is checked against it from then on.

FAQ

Questions about run_sandman_gemma_hygiene

What does the run_sandman_gemma_hygiene tool do? +

Run Gemma-style Sandman hygiene for low-risk validated actions only. Semantic archive stays review-only. It is categorised as a Execute tool in the Mapi Agent Memory MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_sandman_gemma_hygiene? +

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

run_sandman_gemma_hygiene is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_sandman_gemma_hygiene? +

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

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

run_sandman_gemma_hygiene 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 → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →