set_ai_log_export_config

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 70 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/set-ai-log-export-config.md

WHAT IT DOES

What set_ai_log_export_config does on Meridian

AI agents use set_ai_log_export_config 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
`enabled`	boolean	—	Per-project override. false force-disables even if the global flag is on; true/omitted defers to the global flag.
`protocol`	string	—	Documentation-only label; both send the same OTLP/HTTP wire format.
`project_id`	string	—
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given.
`service_name`	string	—	OTel resource service.name override for this project's exported events.
`otlp_endpoint`	string	—	http:// or https:// OTLP logs endpoint override for this project. Validated — never a secret-shaped or embedded-credential URL.
`langfuse_compat`	boolean	—	Informational hint only — set true when otlp_endpoint points at a self-hosted Langfuse OTLP-compatible ingestion endpoint.

Parameters from the server's own tool schema.

RISK

Why set_ai_log_export_config is rated Medium

An AI agent can call set_ai_log_export_config 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.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_ai_log_export_config Rate-limited

set_ai_log_export_config 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_ai_log_export_config": {
      "limits": [
        {
          "counter": "set_ai_log_export_config_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 set_ai_log_export_config call is checked against it from then on.

FAQ

Questions about set_ai_log_export_config

What does the set_ai_log_export_config tool do? +

[MAINTENANCE] R2-G — Set per-project override config for the OPTIONAL AI-log -> OTel/self-hosted-Langfuse export adapter. Every field is optional and left-as-is when omitted (partial upsert). 'enabled=false' force-disables export for THIS project even when the global MERIDIAN_AI_LOG_OTEL_ENABLED flag is on; 'enabled=true' or omitted defers to the global flag — a project can never turn export on when the operator has globally disabled it. 'otlp_endpoint' must be an http:// or https:// URL and is validated against this codebase's shared secret/path checks (meridian.secret_redaction.check_for_secrets + meridian.capability_manifest's embedded-credential/absolute-path patterns) — rejected with a ValueError if it looks like it carries a bearer token, embedded basic-auth credentials, or a machine-local path. An OTLP auth header/API key is NEVER accepted here — set the MERIDIAN_AI_LOG_OTEL_HEADERS environment variable on the server instead; there is no field on this tool or column in storage for it. 'langfuse_compat=true' is a purely informational hint (adds a resource attribute, shown in get_ai_log_export_status) for pointing otlp_endpoint at a self-hosted Langfuse OTLP-compatible ingestion endpoint — it does not change the wire protocol. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata -- including task log entries, pinned decisions, sprint items, notes, handoff/goal state, and HITL queue items -- are sent to and stored in Meridian's service, in an isolated per-tenant Postgres database (Neon); self-hosted deployments keep the same categories in the configured local SQLite/Postgres database. This data is visible in the dashboard and API, and may resurface in later project context or handoffs. Notes and pinned decisions can be deleted individually; task log entries and sprint items can be deleted via the dashboard/API (not exposed as an agent-facing tool); HITL queue items and handoff state have no per-record delete. Full removal of any of this data is available via project or account deletion, 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 set_ai_log_export_config accept? +

set_ai_log_export_config accepts 7 parameters: enabled, protocol, project_id, project_name, service_name, otlp_endpoint, langfuse_compat. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_ai_log_export_config? +

Register the Meridian MCP server in PolicyLayer and add a rule for set_ai_log_export_config: 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 set_ai_log_export_config? +

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

Can I rate-limit set_ai_log_export_config? +

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

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

set_ai_log_export_config 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 235 Meridian tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server → The MCP Attack Database →

Guides

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