activate_profile_layer

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/activate-profile-layer.md

WHAT IT DOES

What activate_profile_layer does on Meridian

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

Parameter	Type	Required	Description
`actor`	string	—	Optional human/session identity recorded on the audit ledger for this transition.
`scope_id`	string	Yes	The hosted_default scope id to activate (typically 'global').

Parameters from the server's own tool schema.

RISK

Why activate_profile_layer is rated Medium

An AI agent can call activate_profile_layer faster than any human can review: one bad instruction and it creates or modifies resources in Meridian by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs activate_profile_layer safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For activate_profile_layer, this is the rule to start with:

activate_profile_layer Rate-limited

activate_profile_layer 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": {
    "activate_profile_layer": {
      "limits": [
        {
          "counter": "activate_profile_layer_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 Meridian, apply this rule, and every activate_profile_layer call is checked against it from then on.

FAQ

Questions about activate_profile_layer

What does the activate_profile_layer tool do? +

[SUPPORT] 0bec79a7 (PROFILE-5) — Advance a hosted_default layer's lifecycle to 'active' — the single 'publish' operation for the hosted_default floor (fae6e882 pinned decision collapsed 'publish' and 'activate' into this one tool: a hosted_default layer becomes authoritative the moment it reaches 'active', so there is no separate publish step to expose). Only a draft -> active or deprecated -> active transition is valid; any other current state (e.g. retired, which is terminal) rejects with {error}. Idempotent: calling on an already-active scope is a no-op success (same revision, no new audit row). See reset_profile_layer for the non-audited 'clear the row entirely' path, or save_profile_layer followed by this tool for the audited draft-then-publish flow. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and stored in Meridian's service; self-hosted deployments keep them in the configured local SQLite/Postgres database. This data is visible in the dashboard/API and later project context or handoffs. Delete individual tasks, notes, or decisions where supported, or delete the project/account using the documented controls. Do not include secrets. It is categorised as a Write tool in the Meridian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does activate_profile_layer accept? +

activate_profile_layer accepts 2 parameters: actor, scope_id. Required: scope_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on activate_profile_layer? +

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

What risk level is activate_profile_layer? +

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

Can I rate-limit activate_profile_layer? +

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

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

activate_profile_layer is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meridian, and thousands of servers like it.

This server

All 175 Meridian tools →

Across the catalogue

The MCP Attack Database →

Guides

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