set_active_context · Mnehmos Synch MCP: Risk & Policy

WHAT IT DOES

What set_active_context does on Mnehmos Synch

AI agents use set_active_context to create or update resources in Mnehmos Synch — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mnehmos Synch environment.

WHY IT NEEDS A POLICY

Why set_active_context needs a policy

This tool creates or modifies data (the active context state for a project) in a reversible manner. It does not execute arbitrary operations, delete data irreversibly, or move money.

From the tool's definition Tool description states 'Update the active context for a project' and 'persist your current working state', indicating modification of stored project state data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_active_context Rate-limited

set_active_context 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_active_context": {
      "limits": [
        {
          "counter": "set_active_context_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about set_active_context

What does the set_active_context tool do? +

Update the active context for a project. Use this to persist your current working state. It is categorised as a Write tool in the Mnehmos Synch 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_active_context? +

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

What risk level is set_active_context? +

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

Can I rate-limit set_active_context? +

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

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

set_active_context is provided by the Mnehmos Synch MCP server (mnehmos/mnehmos.synch.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.