recalculate_memory_tiers · Semantic Context MCP

WHAT IT DOES

What recalculate_memory_tiers does on Semantic Context MCP

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

WHY IT NEEDS A POLICY

Why recalculate_memory_tiers needs a policy

The tool modifies stored data (tier classifications) in a reversible way without permanently destroying records or executing arbitrary code. It updates internal state for the memory/context system. This is Write rather than Execute because it applies a deterministic classification logic rather than running arbitrary operations.

From the tool's definition Tool name and description indicate 'Update tier classifications' - a modification operation that changes data state based on temporal logic. The word 'Update' is a direct indicator of Write category.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

recalculate_memory_tiers Rate-limited

recalculate_memory_tiers 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": {
    "recalculate_memory_tiers": {
      "limits": [
        {
          "counter": "recalculate_memory_tiers_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 Semantic Context MCP, so you can run agents against it safely.

FAQ

Questions about recalculate_memory_tiers

What does the recalculate_memory_tiers tool do? +

Update tier classifications based on current time. It is categorised as a Write tool in the Semantic Context MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on recalculate_memory_tiers? +

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

What risk level is recalculate_memory_tiers? +

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

Can I rate-limit recalculate_memory_tiers? +

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

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

recalculate_memory_tiers is provided by the Semantic Context MCP server (semanticintent/semantic-wake-intelligence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.