memento_toggle_active_coercion · Memento MCP: Risk & Policy

WHAT IT DOES

What memento_toggle_active_coercion does on Memento

AI agents invoke memento_toggle_active_coercion to trigger actions in Memento. 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.

WHY IT NEEDS A POLICY

Why memento_toggle_active_coercion needs a policy

This tool toggles Active Coercion which includes triggering IDE notifications and enabling/disabling pre-commit blocking — these are external operations that affect the development environment and git workflow. Toggling blocking behavior on pre-commits can have significant impact on code delivery pipelines.

From the tool's definition Toggle deterministic Active Coercion (IDE notifications and pre-commit blocking) for the current workspace

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memento_toggle_active_coercion Rate-limited

memento_toggle_active_coercion 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": {
    "memento_toggle_active_coercion": {
      "limits": [
        {
          "counter": "memento_toggle_active_coercion_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Memento, so you can run agents against it safely.

FAQ

Questions about memento_toggle_active_coercion

What does the memento_toggle_active_coercion tool do? +

[DEPRECATED] Toggle deterministic Active Coercion (IDE notifications and pre-commit blocking) for the current workspace. It is categorised as a Execute tool in the Memento MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on memento_toggle_active_coercion? +

Register the Memento MCP server in PolicyLayer and add a rule for memento_toggle_active_coercion: 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 Memento. Nothing to install.

What risk level is memento_toggle_active_coercion? +

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

Can I rate-limit memento_toggle_active_coercion? +

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

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

memento_toggle_active_coercion is provided by the Memento MCP server (joyciakira/memento). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.