log_task

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 62 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/log-task.md

WHAT IT DOES

What log_task does on Meridian

AI agents use log_task 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
`kind`	string	—	Entry taxonomy. shipped=work done, found=discovery, decided=arch choice, blocked=blocker.
`status`	string	—
`project_id`	string	—
`session_id`	string	Yes
`description`	string	Yes
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given.

Parameters from the server's own tool schema.

RISK

Why log_task is rated Medium

This tool writes persistent records (task logs with status and metadata) to a database (local or hosted). It creates/modifies stored data reversibly — individual tasks can be deleted via documented controls. The main risk is data persistence and potential exposure of sensitive information sent to an external service, but it does not execute code, destroy data irreversibly, or involve finances.

From the tool's definition 'Log a task this session completed or is working on' and 'supplied text and project/session metadata are sent to and stored in Meridian's service' and 'This data is visible in the dashboard/API and later project context or handoffs'

Attacks that exploit this kind of access

RECOMMENDED RULE

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

log_task Rate-limited

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

FAQ

Questions about log_task

What does the log_task tool do? +

[SUPPORT] Log a task this session completed or is working on. Valid statuses: pending, in_progress, done, failed, backlog, future, backburner. 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 log_task accept? +

log_task accepts 6 parameters: kind, status, project_id, session_id, description, project_name. Required: session_id, description. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on log_task? +

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

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

Can I rate-limit log_task? +

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

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

log_task 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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server → The MCP Attack Database →

Guides

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